search_prompts

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

No annotations provided, so the description carries the burden. It mentions 'tested, community-rated prompts' hinting at result quality, but lacks details on pagination, ordering, or error handling. Adequate for a read-only search.

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?

Extremely concise and well-structured: purpose first, then parameter descriptions with examples. No unnecessary words, every line earns its place.

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?

Covers essential aspects for a simple search tool: purpose, usage, and parameter details. Lacks output format or result count info, but acceptable given no output schema and low complexity.

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?

With 0% schema coverage, the description compensates by providing examples for query and listing allowed categories for category. However, it doesn't confirm if the categories are exhaustive or if additional free-text is allowed.

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?

Clearly states the tool searches the prompt library by keyword or category, with specific examples. The purpose is distinct from siblings like get_prompt (single prompt retrieval) and list_popular_prompts (trending prompts).

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?

Implies usage for finding prompts via search terms or categories, but does not explicitly state when to use alternatives or exclusions. The sibling context is available but not integrated into the description.

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