pid

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

Annotations declare readOnlyHint=false, which already signals mutation. The operation names (insert, draw, connect, add) are consistent with that. However, the description adds no behavioral context beyond the operation list—no prerequisites, side effects, state changes, or error behavior. For a tool with many mutating operations, this is a meaningful gap.

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 a compact bulleted list, front-loaded with the tool's general purpose. Each line enumerates an operation and its data payload with no filler. It is concise and well-structured for quick reference.

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?

With many operations and an output schema, the description provides a useful reference but lacks context about sequencing (e.g., 'setup_layers' may need to run first), return values, or whether a drawing must be open. The include_screenshot parameter is not explained either. It is adequate but not complete for an agent to fully plan multi-step workflows.

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%, but the description fills in the data shapes for each operation, e.g., 'insert_symbol — data: {category, symbol, x, y, scale?, rotation?}' and 'add_flow_arrow — data: {x, y, rotation?}'. This is essential for constructing valid data objects. Still, it doesn't enumerate allowed values for fields like category or valve_type, and coordinate units are not specified.

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 opens with 'P&ID drawing with CTO symbol library' and lists concrete operations (insert_symbol, draw_process_line, etc.). This clearly communicates the tool's scope. However, the top-level statement is a noun phrase rather than an explicit verb+resource, and it doesn't directly distinguish from sibling tools beyond listing specialized operations.

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?

Usage is implied by the list of operations: it's for P&ID drawing tasks like inserting symbols and drawing process lines. There is no explicit 'use this when...' or mention of alternatives, and no guidance on when not to use it. Sibling tools like layer, drawing, and entity suggest other areas, but the description doesn't clarify the boundary.

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