search_articles

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

No annotations provided; description only mentions search fields. Does not disclose case sensitivity, partial matching, pagination behavior, or any further constraints, leaving agent uncertain about search mechanics.

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 sentence, no filler, all words carry meaning. Efficient and well-structured.

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 output schema exists, description does not need to explain return values. Covers search scope and parameter hint, but lacks details on result ordering, error handling, or pagination. Adequate but not exhaustive.

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 coverage is 0%, so description must compensate. It clarifies that 'query' searches title, slug, and description, but does not explain the 'limit' parameter beyond its schema default. Partial addition but 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?

Description uses specific verb 'Search', identifies resource 'articles', and lists fields 'title, slug or description', clearly distinguishing from sibling tools like get_article or list_articles.

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 when-to-use or alternatives mentioned. Implication is clear for searching but lacks guidance on when to use sibling tools like get_article for exact article retrieval or list_articles for unfiltered listing.

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