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

The 'Read-only' line just restates readOnlyHint and earns no credit, but because there is no output schema, enumerating the returned fields is genuine behavioral disclosure that the agent could not get from structured data. It still omits page-size defaults in practice (deferred to schema) and any note on total/next_offset presence in the response.

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?

Tight and front-loaded: the resource and return fields come first, then the cross-tool hint. Minor waste in 'Read-only' (already an annotation) and 'GET /forms' (implementation detail), but no sentence is bulk.

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 two-parameter read-only list with no output schema, the description covers resource, return shape, and downstream id usage, while annotations carry the safety profile and the schema carries pagination. The only remaining gap is response envelope detail (whether a total or next_offset is returned).

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 100%, and the schema already explains count range/default and that next_offset from the prior reply drives offset. The description adds nothing about either parameter, so the baseline 3 applies.

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?

Specific verb + resource ('List the MoonClerk payment forms') plus the exact fields returned (id, title, currency, payment_volume, successful_checkout_count, timestamps). The singular sibling moonclerk_get_form and the other list_* siblings are separable purely on resource/verb, so no ambiguity remains.

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?

It gives downstream guidance ('Use the form ids to filter customers (plans) and payments'), which implies when the tool is useful, but never states when to prefer it over moonclerk_get_form or the other list tools, and offers no exclusions or prerequisites.

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