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

No annotations are provided, so the description must carry the behavioral burden. It does disclose that the output is summaries, not full step-by-step instructions, and lists the fields included in each summary. However, it does not describe pagination behavior, category filtering, or what 'every published guide' means in relation to limit/offset.

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 two sentences with no wasted words. The first sentence front-loads the return fields, and the second sentence concisely states the downstream use case.

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 listing tool with three optional parameters and no output schema, the description covers the core purpose and relationship to get_opt_out_instructions. It is incomplete, though, because it doesn't explain the optional filters, default pagination behavior, or how to differentiate this tool from search_privacy_library.

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 description coverage is 0%, and the description does not explain limit, offset, or category at all. Listing 'category' among returned fields gives a weak clue, but it never indicates that category can be used as a filter. The agent is left to infer parameter meaning solely from names and the schema enum.

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 clearly states the tool lists summaries of published opt-out guides and enumerates the returned fields (slug, domain, category, method, difficulty, turnaround, support level). It explicitly positions this as a precursor to get_opt_out_instructions, giving it a distinct role among siblings. It does not explicitly contrast with search_privacy_library, another discovery-focused 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?

The description explicitly says 'Use it to find the right slug before calling get_opt_out_instructions,' which provides a clear when-to-use context. It does not mention exclusions or when to prefer search_privacy_library or other alternatives, so it falls short of a full decision framework.

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