abstract_petri_net

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

With no annotations provided, the description carries full burden. It discloses internal wrapping (net_to_descr) and the behavioral trait that 'truncated' is always false due to missing MAX_LEN parameter. No contradictory information, but could mention read-only nature or return format beyond enumeration.

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 four sentences, each adding value: purpose, internal mechanism, output elements, and a behavioral note. No redundancy or fluff. Front-loaded with the core action.

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 a single parameter and output schema presence, the description covers the main purpose, input source, output content, and a relevant behavioral detail. It is sufficient for decision-making, though could mention that the output is textual and what the output schema provides.

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 sole parameter 'petri_id' has 0% schema description coverage. The description hints it's an identifier from discover_petri_net but does not explain format, origin, or validity rules. More explicit parameter guidance is needed to compensate for schema 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 verb 'Describe' and resource 'Petri net', specifying it takes a net from 'discover_petri_net'. It distinguishes from siblings (other abstract_* and visualize_petri_net) by focusing on natural language output and enumerating specific elements (places, transitions, arcs, markings).

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?

The description implies usage after discovering a Petri net ('from discover_petri_net') and notes that truncation never occurs. However, it lacks explicit when-to-use vs alternatives, such as comparing to visualize_petri_net or other abstract tools. No exclusions or prerequisites are clearly stated.

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