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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuine beyond-annotation context: it takes no input, it is unauthenticated ('No key needed'), and the content is served 'in the site's own words' with outbound links. It does not need to describe return formatting since there is no output schema.

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-loaded with 'Use this when', followed by what it returns and then the two explicit exclusions. Four sentences, none redundant, and the auth detail is a short trailing clause rather than a paragraph.

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 zero-parameter, read-only introspection tool with no output schema, the description covers invocation (no input, no key), output contents (description, status, operator, links), and routing boundaries against both nearest siblings. Nothing an agent needs is missing.

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 has zero parameters, which sets the baseline at 4. The description confirms this explicitly with 'Takes no input', which is accurate and prevents an agent from hunting for an argument object.

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 ('Evictions API' service overview) and enumerates exactly what it returns: the service description, current status, operator, and links to home/how-it-works pages. It explicitly contrasts itself with evictions_get_pricing and evictions_get_state_eviction_facts, so an agent can route without opening any 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?

The description gives the triggering user intent ('what Evictions API is, what is available today, how a real case is handled or who operates it') and then names two exclusions with the sibling to use instead for each. This is explicit when/when-not/alternatives coverage.

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