Edit Geometry

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

Beyond annotations, description reveals partial update behavior ('any argument left out is unchanged') and handle preservation. Annotations only provide readOnlyHint and destructiveHint, which are consistent.

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?

Two concise sentences: first states purpose, second lists parameters per entity type with the crucial note on unchanged args. No wasted words, front-loaded.

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?

Covers essential info: purpose, supported entity types, behavior for omitted parameters. Has output schema, so return values need not be explained. Could mention error cases (e.g., invalid handle) but not required.

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 coverage is 100%, so the description adds no additional meaning over the parameter descriptions. It lists the parameters per entity type but does not provide extra semantics beyond the schema.

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?

Clear verb 'edit' and specific resource 'defining geometry of an existing entity'. Distinguishes from siblings like entity_move or entity_set_properties. Lists applicable entity types (CIRCLE, LINE, ARC).

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?

States 'in place (no delete/recreate)' and lists entity-specific parameters, giving context for when to use. Does not explicitly compare to alternatives like entity_set_properties, but the purpose is sufficiently distinct.

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