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

The description adds substantial behavioral detail beyond the readOnlyHint=false annotation: synchronous execution, a hosted 7,500-row default, a 10-20 second response budget, local-loopback behavior with no service cap, and identifier deduplication. This gives the agent useful expectations about limits, performance, and execution semantics. No contradiction with annotations exists.

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?

The description is three sentences with the core action, resource, and output formats front-loaded. The second and third sentences add capacity, performance, and behavioral context without fluff. Every sentence earns its place.

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 complex tool with 13 parameters, low schema coverage, and no output schema, the description omits critical information: no response/return structure, no explanation of the items array's role, and no mention of the from_system versus geography_binding choice. An agent would still need external schemas or help to invoke this correctly on non-trivial inputs.

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 only 31%, and the description does not explain the core conversion parameters such as from_system, geography_binding, to_system, iso3, limit, min_share, target_admin_level, or relationship_vintage. It adds useful context around output_format and overall item counts, but most of the 13 parameters remain underspecified. The description only partially compensates for the schema's low coverage.

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 description states a specific action and object: 'Creates a synchronous v0 user-data conversion job' and immediately specifies output formats. This goes beyond the title and helps distinguish it from estimate and geometry siblings, though it never explicitly names an alternative. It is clear but sibling differentiation is implicit rather than stated.

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?

There is no explicit guidance on when to use this tool versus estimate_conversion_job, convert_reference, or resolve_reference. The 'synchronous' qualifier hints at immediate conversion use, but no prerequisites, exclusions, or alternative-selection conditions are given. The agent is left to infer routing.

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