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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description goes beyond them by disclosing that the form is added to the user's case (a mutation), the exact URL provenance validation, allowed extensions, and the failure/fallback behavior. It stops short of stating auth or permission requirements.

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?

Four dense lines, each carrying distinct information: action, input constraint, file types, downstream usage, and failure fallback. No filler and the core action is 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?

An output schema exists, so return values need not be described, yet the description usefully points to the returned forms' form_id as the handoff to inspect_form/fill_form. The only real gap is that program_id's meaning is never explained.

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 description coverage is 0%, so the description carries the burden. It richly constrains url (provenance and file extensions) but never explains program_id, leaving half the parameters undocumented.

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+scope: import exactly one municipal official form and attach it to the user's application case. It also names the upstream source (start_application's official_forms) and downstream siblings (inspect_form/fill_form), so an agent can place it in the workflow without opening any schema.

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 explicit trigger (when the user asks), an input restriction (url must come from start_application's official_forms; anything else is rejected), accepted file types, and an explicit fallback path (guide the user to upload_url when import fails). This is when/when-not/alternative guidance in full.

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