uodo_search_decisions

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

No annotations are provided, so the description carries full burden. It mentions sorting (newest first) and that results contain IDs, but it does not disclose other traits like read-only nature, rate limits, or pagination behavior beyond mentioning the 'from' parameter. The description adds some value but is not comprehensive.

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 well-structured with clear sections: purpose, query modes, principle, and other parameters. Each sentence adds value. It could be slightly more concise but remains efficient and easy to parse.

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 has 6 parameters and no output schema, the description covers usage and all parameters adequately. It mentions that results contain IDs for downstream use. However, it does not describe the output structure in detail, which would be helpful for the agent.

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 100%, but the description adds significant meaning for the crucial 'query' parameter by explaining the AND/OR modes with examples. This goes beyond the schema's simple description. For other parameters, the description aligns well with 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 the tool searches UODO decisions and sorts by newest first. It indirectly distinguishes from sibling tools by mentioning that results contain IDs to be used with uodo_get_decision. However, it does not explicitly contrast with siblings, so it's clear but not top-tier.

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 provides detailed guidance on when and how to use the tool, including two query modes (AND vs OR), explanation of other parameters, and a directive not to supplement results with own knowledge. It does not explicitly state when not to use this tool, but the context is sufficient.

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