get_form_submission

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the tool returns a JSON string and enumerates key returned fields, including the `form_data` dict, and explains the optional behavior of `account_id` auto-resolving. However, it does not mention not-found or error behavior, which would make it more complete.

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 well-structured and front-loaded: a one-sentence purpose, a usage context sentence, then compact Args and Returns sections. Every sentence adds value, and there is no filler or repetition.

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 retrieval tool, the description covers what the tool does, when to use it, how the parameters behave, and what the response contains. Although an output schema exists, the description's return-value details make it self-sufficient; no critical calling information 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?

The input schema has no property descriptions (0% coverage), but the description fully compensates: it documents `submission_id` as a 'FOR...' id and explains that `account_id` is a CallRail account ID that auto-resolves if omitted. This adds essential semantic meaning beyond the bare type declarations.

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 states a specific verb and resource ('Get full detail for one form submission') and immediately distinguishes it from list-style operations by emphasizing 'one' submission and 'all submitted field data.' It also references `list_form_submissions`, making the differentiation from its closest sibling explicit.

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 provides clear usage context: fetch a single submission after seeing a submission ID via `list_form_submissions` or in a webhook callback. It does not explicitly state 'use list_form_submissions when you need multiple submissions,' but the single-vs-list distinction is strongly implied.

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