convert_osm_to_idf

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

The description only states the conversion and loading without detailing side effects (e.g., overwriting files, session impact). Annotations indicate idempotent and non-read-only, but the description adds minimal behavioral context beyond the schema.

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?

Extremely concise (one short sentence), but at the cost of missing important usage and behavioral details. Every sentence should earn its place; this one is too terse.

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?

Given the existence of an output schema and a complex conversion task, the description lacks prerequisites, behavioral side effects, and distinction from sibling tools. It does not fully specify what happens to the current session or model state.

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 100%, so the description adds no additional meaning to parameters. Baseline 3 is appropriate since the schema already documents each parameter.

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 clearly states the action (convert) and the resources (OSM model to IDF), and mentions loading. However, it does not differentiate from the sibling tool 'load_model' or clarify if the conversion and loading are always combined.

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?

No guidance on when to use this tool versus alternatives like 'migrate_model' or 'load_model'. The description lacks when-not-to-use or prerequisite information.

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