pid

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

The annotations show readOnlyHint=false, so the agent knows operations mutate state. The description adds context by naming each operation and its data payload, implying effects like inserting a symbol or creating layers. However, it does not disclose prerequisites (e.g., whether setup_layers must be called first), potential overwrites, or error 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 a terse, well-organized list. It front-loads the tool's purpose in the first sentence, then presents each operation on its own line with its data payload. There is no redundant text or filler.

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 (a dispatcher with 12 operations), the description covers the operation catalog and their data formats well. However, it omits usage guidance, does not mention include_screenshot, and lacks information on operation prerequisites or sequencing. The presence of an output schema covers return values, but overall completeness remains moderate.

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 burden is on the description. It does give meaning to 'operation' by listing valid operation names and to 'data' by showing per-operation data structures, but it fails to explain the 'include_screenshot' parameter entirely and does not explicitly state that 'operation' must be one of the listed strings or that 'data' must conform to the selected operation's structure.

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 then enumerates a comprehensive list of specific operations (setup_layers, insert_symbol, draw_process_line, etc.), making the tool's purpose unmistakable. It clearly distinguishes itself from sibling tools by focusing on P&ID-specific symbols and process-line 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?

The description lists operations but provides no guidance on when to use this tool versus its siblings (e.g., 'drawing' or 'entity'). There is no explicit 'use this when...' or 'for generic drawings use drawing tool instead', leaving the agent to infer usage solely from operation names.

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