Set default scenario

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

The description explains the effect on future estimates and defines each option, but does not disclose scope (e.g., session persistence), side effects, or whether it overwrites previous settings. No annotations are present.

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 fluff, critical details front-loaded. Every word earns its place.

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 setter with one parameter and no output schema, the description is largely complete. It explains the effect and options, though it could mention the return value or confirmation.

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?

The description adds meaning to the enum parameter by explicitly defining each value ('conservative = lowest...', etc.), compensating for zero schema description coverage. The definitions are clear and concise.

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 explicitly states the tool sets the default confidence scenario for future estimates, with a clear verb ('Set') and resource ('default scenario'). It distinguishes itself from sibling tools, which focus on analysis, scoring, or logging.

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 before making estimates, but lacks explicit guidance on when to use or avoid this tool. No alternatives are mentioned, though no sibling directly conflicts.

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