search_posters

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description bears full responsibility for behavioral disclosure. It does not mention whether this is a read-only operation, what the output format is (no output schema), whether results are paginated, or any limits on data scope. The 'local archived' qualifier hints at scope but lacks detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single, complete sentence that is front-loaded with 'Search local archived poster metadata' and then enumerates filter categories efficiently. No fluff, but it could be slightly more structured for readability (e.g., bullet points).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 15 parameters (none required), no output schema, and no annotations, the description is inadequate. It does not clarify how the search behaves (e.g., case sensitivity, wildcard support), whether multiple filters are conjunctive, or what the response contains. The tool appears complex, and the description only lists filters without operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description lists all parameter categories (date, layout, purpose, style, feedback tags, free text, VAT policy, table structure) but does not clarify how parameters combine (AND/OR logic), whether they are optional filters, or any nuances like the 'recentMonths' vs 'month'/'year' precedence. The enum values provide some semantics, but the description adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search local archived poster metadata' with a specific verb and resource, and lists the search dimensions (date, layout, purpose, etc.). It distinguishes from sibling search tools like search_posters vs. get_poster, though it doesn't explicitly differentiate from potential other search functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. While the list of filters implies use cases, there is no mention of when to prefer this over create_poster, get_poster, or recommend_poster_style. Missing exclusions or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.