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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context by promising the full text content rather than a summary or list, and by giving example topic values. No contradiction with annotations.

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 sentence that front-loads the core action and output, with parenthetical examples that add practical guidance without bloat. 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 one-parameter read-only tool with no output schema, the description covers the invocation path, the expected return (full text), and the topic scope. Nothing essential is missing for an agent to call it correctly.

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 schema already documents the 'topic' parameter completely, so the baseline is 3. The description adds value by giving concrete topic examples (docker, cloudformation, cost, aurora, kubernetes, …) and framing the parameter as the direct access key for retrieving the cheatsheet.

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 action ('jump straight to'), a specific resource ('cheatsheet by topic'), and the expected output ('get its full text'). The topic examples and direct-access framing distinguish it from list/browse siblings like list_cheatsheets and browse_by_tag.

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 use case is implied: use this when you already know the topic and want the full cheatsheet text. However, it does not explicitly say when to use list_cheatsheets, list_topics, browse_by_tag, or get_commands instead, nor does it mention any exclusions.

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