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

Annotations already declare readOnlyHint/destructiveHint, but the description adds behavior the annotations cannot: no pagination on the response, a specific 404 'Submission not found' failure mode, and the livemode toggle for test-mode records. The read-only constraint is restated with an actionable fallback for write requests, which is genuinely useful context.

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 core purpose, then layered with usage, error behavior, examples, and the read-only caveat. Well-structured, though the four example queries and the bolded read-only paragraph push it slightly beyond the minimum an agent needs.

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 single-record getter with an output schema, an agent needs purpose, discovery path, test-mode handling, and failure semantics — all present. Return-value structure is properly delegated to the output schema, so nothing essential is missing.

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%, so both parameters are already documented, making 3 the baseline. The description adds modest value by restating the livemode test-mode behavior and by tying the ID parameter to the discovery workflow, but it introduces no format or syntax detail the schema lacks.

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 — 'Retrieve a single form submission by ID from your Checkout Page account' — and immediately establishes scope (one record, by ID, no pagination). It is clearly distinguishable from the sibling `list_submissions`, which it names explicitly.

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?

Tells the agent exactly when to use this versus the alternative: 'Use `list_submissions` first if you need to discover a submission ID by customer email, customer name, page, customer ID, or date range.' It also routes modification intents away from MCP toward the dashboard, so both the when and the when-not are covered.

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