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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description's added value is disclosing the return payload's composition, which matters because there is no output schema. It omits edge behavior such as invalid-slug handling or document size, keeping it below a 5.

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 compact sentence with zero waste, and the payload contents are front-loaded so an agent can decide quickly whether this is the right tool.

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?

With no output schema, the description usefully enumerates what the response contains, and the one required parameter is fully documented in the schema. Missing only minor operational details (failure modes on unknown slugs, output length) to be fully complete.

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?

There is a single parameter with 100% schema description coverage, including a concrete example ('sign-in-engine') and a pointer to search_docs, so the baseline is 3. The description contributes no additional slug semantics such as case sensitivity or format rules.

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 precisely enumerates what is returned — steps, code, settings, safety notes, troubleshooting — so an agent knows this is a full-content retrieval tool, not a search. The title supplies the verb ('Read'). It stops short of differentiating itself from the sibling get_recipe, which likely returns similarly structured recipe content, so the agent must infer the guide/recipe distinction.

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: 'one Claspine guide' signals that a specific guide must already be identified, so discovery should precede this call. The schema's slug description points to search_docs, but that routing cue lives in the schema, not the description, and no when-not-to-use case (e.g. versus get_recipe or api_reference) is stated.

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