Get AIOrouter Presets

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

Annotations already declare readOnlyHint=true, and the description adds that it shows a triple preset configuration. This adds content context but does not disclose additional behavioral traits like output format, latency, or any side effects. The description is consistent with the annotation, so no contradiction.

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 one short, direct sentence that front-loads the verb and resource. Every word contributes to meaning with no redundancy or filler.

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 zero-parameter read-only tool with no output schema, the description is sufficient to understand purpose and content. It could add a hint about the exact structure of the returned presets, but the current text makes it clear enough. The low complexity and existing annotation support completeness.

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?

There are zero parameters, so the schema is complete and the description naturally adds no parameter-specific info. However, the description enriches understanding by specifying that the output contains planner/coder/reviewer roles, which is valuable beyond the empty schema. Baseline 4 for zero-parameter tools.

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 has a specific verb ('Show') and a specific resource ('triple preset configuration') with clarifying context ('for CODE-MAS orchestrator'). It clearly distinguishes from sibling tools like get_usage, get_pricing, and get_model_info.

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?

Usage is implied from the name and description: if you want to see the configured presets, use this. However, there is no explicit 'when to use' or 'when not to use' guidance, nor any mention of alternatives such as export_config or compare_models.

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