pid

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

The description lists mutating operations (setup_layers, insert_symbol, etc.), consistent with readOnlyHint=false. However, it does not disclose side effects, persistence requirements, or whether operations are reversible. It provides more than a tautology but lacks deeper behavioral context like permission needs or transaction behavior.

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 efficiently structured as a bullet-like list with no redundant prose. It front-loads the purpose and then lists operations with their data fields in a scannable format. A few operation details are terse, but overall the compactness is appropriate for the information conveyed.

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 the existence of an output schema (not shown) and generic input schema, the description provides the essential operation dictionary and data shapes, which is critical for correct invocation. It lacks examples or enumerations of valid symbol/category values, but for a tool of this complexity, it covers the main invocation paths adequately.

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% for the top-level parameters, but the description compensates by specifying the allowed 'operation' values and the expected 'data' payload for each operation (e.g., insert_symbol with category, symbol, x, y). It does not explain the 'include_screenshot' parameter, which is a minor gap. The detailed operation list provides substantial semantic value beyond the generic 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?

The description clearly identifies the tool as 'P&ID drawing with CTO symbol library' and enumerates specific operations (setup_layers, insert_symbol, etc.), making the purpose evident. It does not explicitly contrast with sibling tools, but the focused domain and operation list distinguish it from generic tools like 'entity' or 'drawing'.

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 when to use the tool (for P&ID drawing operations) but does not explicitly state alternatives or exclusions. It offers no guidance such as 'use this for P&ID symbols, use entity for generic entities', but the operation list itself conveys that this is the place for P&ID-specific tasks.

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