ask-one

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

Annotations already declare readOnlyHint=true, and description adds 'Advisory, single-shot' and 'Returns the standard result envelope'. Does not detail behavior on failure or other traits, but complements annotations adequately.

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 covering purpose and usage, front-loaded. Some redundancy (e.g., 'advisory, single-shot' could be merged) but overall efficient.

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?

With 7 parameters and no output schema, description lacks essential parameter explanations and return details beyond 'standard result envelope'. Many sibling tools exist, but description doesn't aid in distinguishing further or guiding parameter usage.

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 only 14% (only provider has a description). Tool description expands on provider ('e.g. codex, openrouter:<alias>') but leaves other 6 parameters (prompt, expert, developerInstructions, etc.) unexplained. Fails to compensate for low schema coverage.

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?

Clearly states 'Second opinion from ONE named provider in the active panel' with verb+resource. Distinguishes from siblings like 'ask-all' and specific provider tools by focusing on a single named provider. References 'panel' to get provider names.

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?

Provides usage context: 'Issue N of these in parallel...', describes render behavior. Mentions 'Advisory, single-shot' indicating non-decisive nature. Does not explicitly list when not to use, but guidance is clear.

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