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

Annotations supply only destructiveHint=true. The description adds meaningful context beyond that: real records are created, the form's integrations are triggered as a side effect, submissions are capped at 10, and payments are recorded without charging anyone. This is more than the annotation conveys.

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?

Three front-loaded sentences plus the underlying endpoint; the purpose, the import use case, required vs optional fields, and the side-effect warning each appear once with no padding.

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 write tool with no output schema, the description covers purpose, limits, required fields and side effects. It omits what the call returns (e.g. created submission ids) and any partial-failure behavior, which are the only notable gaps.

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 value: it separates the required question answers from the optional URL parameters, scheduling, payments, login email and timestamps, and ties question ids back to fillout_get_form. It doesn't explain answer value shaping beyond what the schema says.

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+resource ('Create up to 10 new submissions on a form') and scopes it precisely against siblings like fillout_list_submissions and fillout_get_submission. The 'as if respondents had filled it in' framing clarifies exactly what kind of record is produced.

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 a concrete use case ('import responses collected elsewhere') and a prerequisite that question ids come from fillout_get_form, plus the 10-item cap. It does not explicitly state when not to use this tool versus alternatives, but the context is clear enough to route an agent.

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