aries_search

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

No annotations provided. Description mentions return format (path, heading, preview) but omits search behavior details like case sensitivity, pagination, or permissions. Lacks depth for a search tool.

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?

Two sentences, no filler. First sentence defines scope and output; second sentence suggests next step. Efficient but could use bullet structure for clarity.

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?

No output schema; description gives minimal return info. With 2 params and 0% schema coverage, description should elaborate on inputs and outputs. Incomplete for a search tool.

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 has 0% coverage; description does not explain 'query' or 'limit' parameters. No details on expected formats or defaults. Fails to compensate for missing schema documentation.

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?

Specifies verb 'Search' and resource 'documentation corpus'. Lists covered sections and explicitly distinguishes from sibling aries_doc by directing to call it next. However, does not differentiate from other siblings like aries_full_doc.

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?

States 'Call aries_doc next' giving usage context. But no explicit when-to-use or when-not-to-use compared to other tools. Only implies flow.

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