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

With no annotations, the description carries the full burden and does well on the non-obvious parts: it discloses the $0.01 USDC cost, explains that the call returns x402 payment requirements, and that the agent's wallet executes the payment. It omits failure/error behavior and any rate or auth constraints, but the payment mechanics are the critical disclosure for this tool.

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 the purpose, then outputs, then cost/payment, then an example — every line earns its place and nothing is padded. The example is short and directly actionable.

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 enumerating return fields is slightly redundant but harmless, and the description correctly spends its budget on what the schema cannot convey: the paid x402 flow and per-call price. Missing only error/quota behavior, which is minor for a read-only domain check.

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?

There is a single parameter with 0% schema description coverage, and the description compensates with a concrete call example (ssl_check(domain="acme.com")) that fixes the expected format. It does not define edge cases (bare domain vs URL vs subdomain), but the example adds real value over the bare string 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 ('SSL/TLS certificate check') plus the exact payload (issuer, expiry, days remaining, TLS version, risk flags), so the agent knows precisely what this returns. It does not, however, contrast itself with domain-adjacent siblings such as dns, headers, or domain_intel, leaving the boundary to inference.

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?

Usage is only implied through the 'lead data' framing and the risk-flag list — there is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. An agent can infer it is for certificate inspection, but must guess when that beats dns or domain_intel.

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