create_meteorological_station_model

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

With no annotations, the description carries the full burden. It discloses the temporary folder removal after export, which is a notable side effect. However, it doesn't mention other behaviors like overwrite handling, error cases, or permissions, leaving gaps for a tool with this complexity.

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 two sentences, front-loaded with the main action, and includes all key workflow steps (create, export, return, cleanup) without unnecessary detail. 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?

The tool is moderately complex (create, export, inspect, delete), and while the description explains the workflow, it lacks specifics about how images are returned, prerequisites, or failure behavior. Given no annotations or output schema, the description is adequate but not fully complete for a tool of this scope.

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?

The schema already covers 67% of parameters with descriptions (outputPath and overwrite). The description adds no parameter-specific information, but since schema coverage is moderate, the baseline of 3 is appropriate. It doesn't compensate for the un-described layoutProfile parameter, but this is not a major gap.

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 tool creates a new Astah project, exports diagrams to a temporary folder, and returns images for visual inspection. This is a specific workflow that distinguishes it from the sibling tool 'create_astah_model', though it doesn't explicitly mention the 'meteorological station' specialization from the name.

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 is provided on when to use this tool versus alternatives or when not to use it. The description implies a use case (generating images for visual inspection) but does not reference any sibling tools or state exclusions.

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