search_prompts

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explains sorting and tag format but omits important traits such as authentication needs, rate limits, pagination behavior, or what happens with empty queries. This leaves significant gaps for an agent.

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?

The description is very concise at two sentences, front-loading the main purpose. While it is efficient, it slightly underspecifies details, but overall it earns its space with no wasted words.

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 the tool's complexity (5 optional parameters) and the presence of an output schema, the description still lacks crucial context like default behavior when query is empty, result ordering details, or error handling. It feels incomplete for an agent to use effectively.

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%, so the description must add meaning. It explains sort_by values and tags as comma-separated, but does not clarify query, category, or limit parameters beyond their defaults. This partial coverage results in a score of 3, as it adds some value but is incomplete.

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 the tool searches prompts by keyword, category, or tags, which is a specific verb and resource. However, it does not differentiate from siblings like get_trending_prompts or get_category_rankings, which could cause confusion about when to use this tool.

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?

The description gives some guidance on sort_by options and tag format, implying when to use certain parameters. However, it lacks explicit instructions on when to use this tool versus siblings or when not to use it, leaving usage context implied rather than explicit.

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