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

Annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so the safety profile is covered. The description still earns credit by adding 'Fetches nothing' (a static, local dataset rather than a live crawl) and by enumerating what each entry contains, which annotations cannot convey.

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 short sentences, front-loaded with what is returned, then when to call it, then a behavioral caveat. No repetition of the title and nothing that could be cut.

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 carries the burden of describing return content, and it does so by listing the four attributes per crawler. Field names and ordering remain unspecified, which is a minor gap for a zero-argument lookup tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The sentence 'Fetches nothing' usefully confirms no filter or scope arguments exist.

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?

Specific verb plus resource ('Lists the 10 AI crawlers Citehound tracks') with the payload spelled out: company, allow/block meaning, and generator default. It also names the sibling it feeds (generate_robots_txt), so an agent can separate it from scan_site or get_methodology without opening a schema.

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?

'Use before generate_robots_txt if you need the exact tracked names' names both the alternative and the condition that selects this tool. It stops short of an explicit when-not-to-use statement, but the conditional framing makes the boundary clear enough to act on.

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