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

Annotations already indicate a non-read-only, open-world, non-destructive operation; the description adds real value beyond them by disclosing the URL provenance restriction (a security/validation constraint), the accepted file extensions, and what to do on failure (surface upload_url to the user). It does not say what happens when case_id is omitted/null or whether an import is idempotent/reversible, which keeps it below a 5.

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 tight sentences, front-loaded with the action and cardinality, then constraint, then next step, then failure path. No filler and no repetition of the title.

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 explained, and the description still usefully names the forms[].form_id field for the next step. The remaining gap is behavioral edge cases (case_id null, duplicate imports, other failure modes), which the fallback sentence only partially covers.

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% across 3 parameters. The description thoroughly explains the tricky one (url: provenance + extension whitelist) but says nothing about program_id or about when case_id (default null) should be supplied versus left empty — a materially ambiguous choice for an agent attaching a form to a case.

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 様式 (official form) from a 自治体 program page and attach it to the user's application case. It is clearly distinguishable from siblings inspect_form/view_form (read a form) and fill_form (fill one), and the '1件' cardinality is explicit.

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 hard precondition for the url (must be a url taken from start_application's official_forms; anything else is rejected), an allowed-format whitelist, the downstream chain inspect_form→fill_form on the returned form_id, and the fallback to guide the user to upload_url when import fails. When/when-not/alternatives are all covered.

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