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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the specific behavior of returning 'full markdown content and metadata', which is useful context beyond the annotation. It does not contradict annotations, and while it doesn't discuss rate limits or authentication, those are not essential given the read-only nature.

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, front-loaded sentence that states the verb, resource, and method with no wasted words. It is efficient and immediately conveys the tool's purpose.

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?

The tool is simple with one parameter and no output schema. The description states it fetches content and metadata, which is sufficient for an agent to invoke it correctly. The read-only annotation covers safety, and the description fully explains what the tool returns. No additional information is needed.

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 input schema fully documents the 'slug' parameter with an example. The description mentions 'by slug', which aligns with the schema but adds no new information about the parameter format or semantics. Since schema coverage is 100%, the baseline of 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 specific verb ('Fetch') and a specific resource ('a single guide's full markdown content and metadata') with a clear method ('by slug'). It distinguishes from sibling tools like dp_search_guides, which would return multiple guides, and from dp_get_glossary_term and dp_get_tool for other content types.

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 description clearly implies this is the tool to use when you have a specific slug and need the full guide content. It does not explicitly exclude alternatives or mention when not to use it, but the 'by slug' phrasing and the existence of dp_search_guides for searching make the usage context clear. However, it lacks an explicit 'when not to use' statement.

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