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

Annotations already establish the read-only, open-world profile, so the bar is lower. The description adds the enumeration of consensus states (consensus, split, mixed, rejected, open), which is genuinely useful for interpreting output, but says nothing about behavior for unknown crisis ids or data freshness.

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?

A single front-loaded sentence that names the resource first and then the payload. It is dense and slightly run-on with the nested enumeration, but every clause enumerates actual returned data rather than 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 one-parameter read tool with no output schema, describing the response contents (crisis status, headlines, exit paths, votes, consensus enum) is exactly what is needed. Only the absence of error/invalid-id behavior keeps it from a 5.

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 coverage is 100% with an enumerated id, so the schema already carries the parameter burden. The description adds no meaning beyond the schema — it does not explain whether ids are stable slugs, what each topic covers, or what happens on an invalid id. Baseline 3 is appropriate.

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 states a clear verb-resource pairing (retrieve one crisis) and enumerates the returned payload: instrument and direction, related headlines, proposed exit paths with votes and consensus state. It contrasts implicitly with multi-item siblings like get_bridge by emphasizing 'One crisis,' but never names an alternative explicitly. The metaphor ('captain's bridge', 'instrument and direction') adds slight ambiguity about what those fields actually are.

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 only implied: the agent must infer that this is the single-crisis lookup to use once a crisis id is known. No when-to-use condition, prerequisite, or alternative (e.g., get_bridge for the overview, get_vote_results for raw tallies) is stated. The word 'One' hints at the differentiation but does not spell it out.

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