list_reasons

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

The description indicates a read-only operation ('Retrieve'), which aligns with the expected behavior. However, with no annotations provided, it fails to disclose any potential side effects, prerequisites, or response characteristics beyond the basic action.

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 a single, concise sentence that is front-loaded and efficiently communicates the tool's purpose. Every word earns its place with no redundancy.

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?

For a simple list tool with no parameters and no output schema, the description is minimally complete. It could be improved by clarifying the scope (e.g., 'all reasons in the system') or mentioning that it returns unfiltered results, but the current text suffices for basic understanding.

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?

No parameters exist, so the description adds no parameter information. Per guidelines, 0 parameters yields a baseline score of 4, which is appropriate here since no additional meaning is needed.

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 'Retrieve all reason instances' uses a specific verb 'Retrieve' and clearly identifies the resource 'reason instances'. It distinguishes from sibling tools like 'get_reason' (single) and 'list_reasons_by_checker' (filtered) by implying a full list.

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 implies usage for retrieving all reasons but provides no explicit guidance on when to use this tool versus alternatives. It does not say when not to use or mention sibling tools like 'list_reasons_by_checker' or 'list_reasons_by_event'.

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