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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: results come newest first, and draft-preview test entries are silently filtered out unless tests is 'include' or 'only' — a defaulting rule an agent could not infer from the schema alone.

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?

Two compact sentences, front-loaded with the core action and ordering before the edge-case rule about test entries. No filler, though the parenthetical example is the only slightly expendable element.

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 five-parameter, read-only list tool with no output schema, the description covers the filtering quirk but omits pagination guidance (default 50, max 200, offset) and any sense of the record shape returned. Adequate but with clear gaps for an agent that needs to page through results.

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 only 40%, so the description must compensate and it does so well for the tests enum by explaining the exclusion semantics. However, limit, offset, collection and site get no additional meaning from the description, leaving pagination behavior undocumented beyond the bare schema bounds.

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 and resource ('Read records from a collection') and adds the default ordering ('newest first') plus a concrete example (contact form submissions). It is clearly distinct from add_record and delete_record among the siblings, though it does not explicitly say so.

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 implied use case (reading contact form submissions) and explains the test-entry default, but never states when to pick this over alternatives such as list_bookings or get_analytics, nor any prerequisite for the required site/collection pair.

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