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

With no annotations, the description must disclose behavioral traits. It reveals a pricing range but does not state what the tool returns, whether it requires authentication, or if it has side effects. The behavior is largely opaque.

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 phrase with no filler. It is front-loaded with the key qualifier 'Survival menu.' However, the brevity sacrifices clarity, so it does not fully earn a 5.

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 minimal schema and no output schema, the description is too sparse. The term 'Survival menu' is ambiguous, and there is no explanation of the menu's purpose or what a caller should expect. A simple read tool still needs a clearer statement of its function.

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 tool has zero parameters, so the baseline is 4. The description adds contextual meaning about the menu's price range, which, while not parameter-specific, is useful. There is no schema to compensate for, and no parameters need explanation.

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 'Survival menu — launch recovery pricing $0.01–$0.05' gives some content clues but does not explicitly state that this tool reads/retrieves a menu. The verb is missing; the resource is implied by the tool name. It is not a tautology, but the purpose is vague and not clearly differentiated from siblings like read_pricing.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like read_pricing and fetch_catalog exist, but the description offers no comparison or selection criteria, leaving the agent without usage context.

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