imports

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

Annotations declare destructiveHint=true and non-idempotent, and the description usefully narrows that: upload never processes a file, process only fires on an explicit request, and the tool cannot delete import files. It also implies a confirmation gate before deletion. It stops short of describing auth requirements, side effects of configure/validate, or backup behavior.

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 sentences, zero filler, and the purpose is front-loaded before the two safety constraints. Each sentence carries distinct information and nothing is repeated from the annotations or schema.

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 no explanation, and the stage enumeration plus safety caveats cover the behavioral core of a multi-action tool. The gap is that an agent cannot tell which parameters belong to which stage (e.g. whether content_base64 is for upload and field_map_json for configure), which is essential for a 9-parameter action-dispatch tool.

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 9 parameters. The description effectively supplies the value set for the required action_name (the six stages), which the schema leaves as an unconstrained string, but it says nothing about filename, import_id, content_base64, field_map_json, run_backup, limit, or offset, so most parameters remain undocumented in both places.

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 (run) and resource (the Snipe-IT CSV import workflow) and enumerates the six stages the tool drives (list, get, upload, configure, validate, process). This lets an agent identify the tool without opening the schema, and the deletion clause distinguishes it from delete_resource.

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 an explicit trigger condition for the riskiest stage ('process runs only when action_name=process is explicitly requested') and routes deletion to delete_resource 'after separate confirmation'. However it does not say when to use list vs get vs configure vs validate, leaving the ordering of stages to inference.

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