get_form_submission

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

No annotations are provided, so the description carries the full burden. It implies a read-only retrieval operation but does not explicitly state that it has no side effects or require specific authentication. The return description provides some behavioral context but lacks full transparency on constraints.

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?

The description is concise, with a clear purpose statement and structured Args/Returns sections. It avoids unnecessary detail but includes essential guidance. It is well-organized and front-loaded.

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?

Given the simple input schema (2 parameters, 1 required) and presence of an output schema, the description adequately covers the return value contents (submitted_at, customer details, etc.). It does not explain every nested field but is sufficient for an agent to understand what data will be 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?

With 0% schema description coverage, the description adds crucial meaning: it explains the format of submission_id ('FOR...' id) and that account_id is optional and auto-resolves. This goes beyond the bare schema and helps the agent understand parameter values.

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?

The description clearly states the tool retrieves full details for one form submission, including all submitted field data. It distinguishes from sibling tools like list_form_submissions (for listing IDs) and update_form_submission (for modification), providing a specific verb and resource.

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?

The description explicitly suggests use after seeing a submission ID via list_form_submissions or a webhook callback, giving clear context. While it does not explicitly state when not to use, the guidance is sufficient for an agent to decide between this and similar tools.

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