get_form_submission

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

No annotations are provided, so the description must disclose behavior. It only states that it gets full details, implying a read operation, but it doesn't explicitly confirm read-only behavior, nor does it mention prerequisites, rate limits, or what happens if the submissionId is invalid. For a fetch operation, this is thin on behavioral 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?

A single sentence with zero redundancy. It front-loads the action and object, and the 'by its id' qualifier at the end is essential. No wasted words.

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 simple get-by-id operation with one parameter, no output schema, and no annotations, the description is largely sufficient. It tells the agent exactly what it does. Some might argue it could mention response format or error cases, but for this level of simplicity, it's adequate.

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 100% coverage with its own description ('The submission's id'). The description adds no additional meaning beyond the schema, merely restating that it uses an id. Since schema coverage is high, baseline 3 is appropriate.

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 verb (Get), the resource (form submission), and the scope (one specific submission by its id). It also distinguishes from list_form_submissions, which returns multiple submissions, and get_form, which returns the form definition. No ambiguity.

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 purpose is clear: use this when you have a submissionId and need the full details of that specific submission. It implicitly differentiates from sibling tools like list_form_submissions, but it doesn't explicitly state when not to use it or mention alternatives. Still, the context is clear enough for an agent to route correctly.

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