pid

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

Annotations provide readOnlyHint=false (indicating mutations) and a title, but the description adds useful context about what specific drawing operations are available (creating layers, inserting symbols, drawing lines, etc.). However, it doesn't disclose important behavioral traits like whether operations are destructive to existing drawings, authentication requirements, rate limits, or error conditions. The description adds some value beyond annotations but misses key behavioral details.

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 with a brief introductory statement followed by a bulleted list of operations. Each operation is clearly named with its required data fields. While comprehensive, it maintains a clean, scannable format without unnecessary verbiage. The structure helps the agent quickly understand available functionality.

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 tool's complexity (12 operations with varying data structures), the description provides substantial operational detail. With an output schema present, the description doesn't need to explain return values. The main gap is lack of guidance about when to use this versus sibling tools, but otherwise it gives the agent sufficient information to understand what the tool can do.

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?

With 0% schema description coverage, the description compensates well by detailing 12 specific operations with their expected data fields. For example, it specifies that 'insert_symbol' requires {category, symbol, x, y, scale?, rotation?} - providing semantic meaning that the bare schema lacks. The description effectively documents the 'operation' parameter's possible values and their associated data structures.

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 states this is for 'P&ID drawing with CTO symbol library' and lists specific operations, which gives a general purpose. However, it doesn't clearly differentiate from sibling tools like 'drawing' or 'block' - the relationship to these other drawing-related tools is unspecified. The purpose is somewhat clear but lacks sibling differentiation.

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 is provided about when to use this tool versus the sibling tools like 'drawing', 'block', 'layer', or 'annotation'. The description simply lists operations without context about appropriate use cases, prerequisites, or alternatives. The agent must infer usage from the operation names alone.

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