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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: retired sites return what-to-do-now guidance without historical actionable forms, and the payload includes a content review date plus a separate current native verification. It does not say what happens on an unknown broker (error vs. empty), which is the one remaining gap.

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?

Three sentences, all load-bearing, with the guide contents front-loaded. The first sentence is a long comma-list that reads as a run-on, but no clause is filler and the retired-site caveat is placed before the input rules where an agent will see it.

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?

There is no output schema, so the description must carry the return contract — and it does, enumerating the guide sections (answer, steps, troubleshooting, FAQs, sources, review date, native verification) and the retired-site fallback. The only omission is failure behavior for an unrecognized or missing broker.

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% and the single parameter is fully documented, so the baseline is 3. The description adds a concrete example ('spokeo') and lists the five accepted identifier forms, and the 'no personal lookup' line clarifies what the field must not contain — reinforcing the schema's 'Never a person's details' warning.

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 verb+resource with full content scope: 'the complete free website guide: direct answer, steps, troubleshooting, FAQs, official sources and content review date, plus separate current native verification.' That distinguishes it clearly from list_opt_out_guides (enumeration) and get_removal_route (routing). It also covers the retired-site variant, so an agent knows the response shape in both branches.

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?

'Accepts a slug (spokeo), domain, name, alias, or URL' and 'No login or personal lookup' give input conventions and a privacy constraint, which implies usage. But it never says when to choose this over get_removal_route or list_opt_out_guides, and no exclusions are stated. Usage is inferable rather than instructed.

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