remove_arc

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

No annotations provided. Description only says 'remove', implying deletion but no details on side effects, requirements (e.g., arc must be disconnected), or return value. Output schema exists but is not referenced.

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?

Very short description with structured Args section. Front-loaded, no wasted words. However, it is too brief to cover necessary details.

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?

Despite simple tool with one param and output schema, description lacks prerequisite info, effect on net state, and return value. Incomplete for safe usage in a complex modeling environment.

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 0%. The docstring says 'arc_id: ID of the arc to remove' which adds minimal context beyond the schema (string). No explanation of what constitutes an arc ID or how to obtain it.

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?

Clearly states 'Remove a single arc from the Petri net.' Verb 'remove' with specific resource 'arc' and context 'Petri net' clearly distinguishes from siblings like add_arc and modify_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?

No guidance on when to use this tool versus alternatives (e.g., modify_arc, remove_place). No mention of prerequisites or post-conditions.

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