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

Annotations already declare readOnly/idempotent/non-destructive/no open world, so safety is covered. The description adds genuinely new behavioral context: that field reports are user-submitted text and marked as such (untrusted-content awareness), and that a 'Dangerous: avoid' label may be present. It omits any statement about slug-not-found behavior or ordering of reports.

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?

Front-loads the resource ('Full Agent Tested record for one tool by slug') before the long enumeration of returned fields. Dense with no filler, though the content list is a run-on that could be grouped more scanably.

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 does the heavy lifting and covers return content thoroughly (verdict, quality, works/breaks, signup/captcha facts, MCP checks, security flags, community verdict, field reports). Gaps remain around report pagination/ordering and error behavior for an invalid slug.

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%, so the description carries the full burden, yet it explains neither parameter. 'By slug' vaguely signals the key but never states the slug format (pattern-constrained) or where to get one beyond the sibling mention; reports_limit (default 5, max 10, min 0) is never referenced, so an agent cannot infer whether 0 suppresses reports or how they are ordered. Only partial compensation for a documented gap.

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 concrete verb+resource with scope: 'Full Agent Tested record for one tool by slug', then enumerates the record's contents. It also names the sibling used to obtain the input ('Get slugs from search_tools'), so an agent can separate this detail-fetch from discovery without opening either 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?

Gives clear context for use (fetch the full record for a single tool, given a slug) and points at search_tools as the source of slugs, which is the key prerequisite. It stops short of explicit when-not guidance or routing against siblings like is_dangerous or check_outages, which also surface overlapping facts.

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