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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it states the tool never charges, never runs research, needs no X-Wallet/Idempotency-Key/PAYMENT-SIGNATURE, and does not consume the shared 10-call trial or paid rate limits. Those are exactly the safety and cost facts an agent needs to decide whether calling it is free.

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 purpose, then usage routing, then behavioral guarantees; every clause carries information. It is dense and slightly cluttered with semicolon-separated fragments, but no sentence is filler.

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?

An output schema exists, so the description need not document return values, yet it still names the fields that survive or disappear under include_backends=false. For a zero-required-param liveness check, everything needed to invoke it correctly and safely is present.

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 there is a single optional param, so the baseline is 3, but the description adds real semantics the schema lacks: omitting it (or true) keeps source_backends while false drops that object while status and payments_ready still return, extra keys are rejected, and {} is valid. Only the default value itself is left to the schema.

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 ('Check MentionForge Worker liveness') and additionally scopes it to a concrete decision ('whether paid research can settle'). Combined with the sibling names it cites, an agent can distinguish this from get_pricing, get_example, and research_mentions 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?

Gives an explicit when-to-use ('free pulse when you only need uptime') plus three named alternatives with the condition that selects each (get_pricing for price/trial terms, get_example for a sample payload, research_mentions for cited mentions). Nothing is left to inference.

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