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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the response is clean Markdown with front matter containing title, URL, dates, and tags — valuable since no output schema exists. It omits any note on truncation or auth/rate limits.

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, front-loaded with the core action and output shape, then the accepted input forms. Every clause carries information; nothing is padding.

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?

Return format is adequately covered despite the absence of an output schema, which is the main thing an agent needs here. Missing pieces are the max_chars truncation behavior and any routing guidance versus search_guides, so it is complete enough to call but not complete enough to choose confidently.

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 50%: slug is documented in the schema, and the description usefully reinforces it with a concrete slug example and the accepted stormap.ai URL form. However, max_chars is undocumented in both places, and its truncation semantics are never explained — a meaningful gap the description fails to compensate for.

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?

States a specific verb and resource ('Return one Stormap guide') plus the output format, which cleanly separates it from the sibling search_guides by scope (one vs. many). It never names the sibling or an alternative, so differentiation is inferred rather than stated.

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 word 'one' plus the accepted slug/URL input implies the retrieval use case, but there is no explicit when-to-use guidance and no mention of when to prefer search_guides instead. Usage is implied rather than directed.

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