get_form_submission

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'Get full detail' with no indication of side effects, authentication needs, rate limits, or whether the operation is read-only. The description fails to compensate for missing 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?

The description is very concise (two sentences). However, the structure uses an 'Args' list format that is not standard for tool descriptions, and the second line feels like parameter docs rather than a natural description. Still, it is short and clear.

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 lack of annotations, low schema coverage (0%), and output schema presence, the description should provide more context. It does not explain what 'full detail' includes, potential response size, or when the submission might not be found. The output schema covers return format, but many operational details are 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 description mentions 'submission_id: 'FOR...' id,' adding format context not in schema. However, the optional 'account_id' parameter is not explained. With 0% schema description coverage, the description partially compensates but leaves a gap.

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 'Get full detail for one form submission,' which clearly identifies the action (get) and resource (form submission). It distinguishes from sibling 'list_form_submissions' by specifying 'one' submission.

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?

No explicit guidance on when to use vs alternatives. The implication is for retrieving a single submission by ID, but there is no mention of when not to use or comparison to other tools like 'list_form_submissions' or 'update_form_submission'.

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