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

Adds substantial behavior beyond the annotations: the source must be publicly accessible or the import cannot read the questions, the result is created as a DRAFT rather than live, un-mappable question types are skipped rather than guessed, and the tool always reports what was imported vs skipped and why. This gives the agent a clear success/failure model with no contradiction against 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?

Three dense sentences, each carrying necessary information: core purpose first, then URL/prerequisite constraints, then the draft output and skip-reporting contract. Nothing is redundant and the most decision-relevant facts are 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?

For a tool with multiple input formats, a prerequisite, a draft output, an explicit next step, and a partial-import failure mode, the description covers every behavior an agent needs to invoke it correctly and set expectations. The output schema exists, so return-structure details need not appear in the description.

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; the description adds genuinely useful detail on top by enumerating the exact acceptable URL patterns (docs.google.com, forms.gle, form.typeform.com/to/..., tally.so) and the public-sharing requirement for the url parameter. The context parameter is already well-specified in the schema with an explicit anti-pattern warning.

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 first sentence states a specific verb ('Convert') with a clear resource (public Google Form, Typeform, or Tally form) and target (a new Clipform), making it distinct from siblings like clipform_create_form (build from scratch) and clipform_update_form (modify existing). The supported-source enumeration removes any ambiguity about what counts as importable.

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 clear usage context: use when converting an existing public form from a supported provider. It explicitly names the follow-up tool, clipform_update_form (is_live: true), for republishing the resulting draft. However, it doesn't explicitly state when-not-to-use versus clipform_create_form, so exclusions are implied rather than explicit.

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