Get a submitted form record

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds substantial extra context: the exact redaction policy, that personal-named fields and media links are withheld unless include_contact_details is set, that free-text names/addresses are not redacted, and that files/media are never downloaded. This is real behavioral disclosure beyond the annotations.

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 and key lookup key, then spends its length on genuinely useful redaction semantics. The middle sentence is dense but every clause carries actionable information; only minor tightening is possible.

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 read-only single-record getter with no output schema, the description covers what is returned (system columns and answers), how to address the record, and the privacy/redaction behavior an agent must anticipate.

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 the baseline is 3, but the description adds meaning beyond the schema for include_contact_details (what it un-redacts, what is never returned, and the free-text caveat) and clarifies that record_id is the search criterion `id`.

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 ('One record submitted on a form'), and the lookup key (record Id). The singular/one-record framing clearly distinguishes it from the sibling list_form_submissions.

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 useful context on how a record Id is obtained (the `id` search criterion of the completedrecords/search endpoint), which implies usage, but never explicitly says when to choose this over list_form_submissions or other siblings, and gives no exclusions.

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