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

The description discloses that the tool is read-only, returns metadata and links rather than full text, and is scoped to how-to guides—none of which is guaranteed by the annotations. There is no contradiction with readOnlyHint=true.

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 resource and examples, with the routing instruction in a short final clause. No filler and no repetition of schema details.

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 an optional-parameter read-only search with no output schema, the description tells the agent what it returns (metadata and links) and how to get full content (dp_get_guide). Remaining details like limit, query, and category are fully documented in the input schema.

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 all three parameters already described. The description adds only 'Filter by category' and topic examples, which map to category and query but do not meaningfully extend the schema's parameter-level documentation.

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 action (Search), a distinct resource (Default Privacy's long-form privacy how-tos), and concrete topic examples like data-broker removal and banking privacy. The closing clause 'use dp_get_guide for full content' differentiates it from the closest sibling.

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?

Provides clear context for use: this is the entry point for long-form guides, returns metadata and links, and explicitly routes to dp_get_guide when full content is needed. It does not explicitly contrast with dp_search_tools or dp_search_glossary, but the resource scoping makes the intended use clear.

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