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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: the IP list changes over time, and the underlying endpoint is GET /ips.json. This is meaningful operational context an agent could not infer from structured fields.

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 tight sentences that front-load what the tool returns and immediately follow with the reason to use it. The parenthetical security note is long but earns its place by discouraging a fragile pattern.

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 read-only, no-parameter list tool with a 100%-covered (empty) schema and no output schema, the description says everything needed: what it returns, why, and the caveat about staleness. Only the exact return shape is unspecified, which is largely self-evident here.

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 for a 0-param tool is 4; the description correctly implies no filtering or input is needed.

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 (List) and resource (DocRaptor IP addresses), and scopes it precisely: the IPs used to fetch remote assets/document_url. This is clearly distinguishable from create_document, get_document_status, and list_documents.

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?

Explicitly names the use case (allowlisting DocRaptor on a firewall or asset host) and points toward the preferred alternative (HTTP Basic auth over IP allowlisting). No explicit 'when not to call' clause, but the practical context is clear.

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