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

The description identifies read-only sub-operations (detect_parts, audit_dimensions) and mentions behavior like undo groups and regen for batch operations. Beyond the annotations (readOnlyHint=false), it adds context but does not fully disclose error states, permission requirements, or the full scope of effects, especially for commit operations.

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 structured as a bullet list of operations, which aids scanning. However, it is quite long and includes repetitive performance rules at the end. Some information could be condensed without loss of clarity.

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 complexity of the tool (many operations) and minimal schema, the description covers the main operations and provides performance rules. However, it omits how output schema looks, error handling, and the relationship to sibling tools. It is adequate but not fully comprehensive.

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 the input schema having 0% parameter description coverage, the description compensates by listing expected data keys for each operation (e.g., create_text expects x, y, text, etc.). This adds significant meaning beyond the generic schema. Some operations are vaguely defined (e.g., dimension_profiles has 'action' but no details), so it's not perfect.

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 tool's domain—text, dimensions, leaders, and automatic dimension workflows. It lists multiple specific operations, making the purpose evident. However, it does not differentiate this parent tool from sibling tools that seem to provide the same sub-operations directly, which could cause confusion.

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 includes explicit performance rules (e.g., use batch or auto_dimension for multiple dimensions, pass region when possible) and notes mutual exclusivity of selection parameters. These provide actionable guidance for efficient tool use. However, it lacks guidance on when to use this parent tool versus the sibling tools.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds that the tool finds specific quality issues, which is consistent and provides useful output context.

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 single 14-word sentence that efficiently lists all audit categories without extraneous text. It is front-loaded and concise.

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 (auditing with multiple issue types) and the presence of an output schema, the description adequately conveys the purpose but lacks context about the input 'data' parameter and how to interpret results.

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 description coverage is 0%, meaning no parameter descriptions exist. The tool description does not mention or explain the 'data' or 'include_preview' parameters, leaving the agent with no semantic guidance beyond parameter names.

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 explicitly lists six distinct types of issues (duplicates, overlap, crossings, missing intent, detached refs, style errors), clearly stating what the tool does. It distinguishes itself from sibling tools that create, plan, or repair dimensions.

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 offers no explicit guidance on when to use this tool versus alternatives like annotation_auto_dimension or annotation_repair_dimension_layout. The usage context is implied but not stated.

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

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

Annotations include destructiveHint=true, but the description does not elaborate on destructive behavior. It adds some context (performance rules) but does not explain side effects or state changes beyond annotations. No contradiction.

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?

Extremely concise: two sentences for core purpose and two performance rules. No redundancy, every sentence adds value.

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?

Despite having output schema and annotations, the description fails to explain the input parameters ('data', 'include_screenshot') or how to construct them. The catch-all 'data' parameter is left ambiguous, making the tool less usable.

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 description coverage is 0% for the two parameters ('data', 'include_screenshot'). The description references parameters like 'region', 'entity_ids', 'selection' that are not in the schema, and does not explain the actual parameters, leaving the agent uninformed.

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 explicitly states the tool's action ('plan and immediately commit dimensions') and resource ('one selected part/region/entity set'). It also distinguishes from sibling tools like annotation_batch_create_dimensions and annotation_plan_dimensions.

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?

Provides clear performance rules: when to use batch vs single, and how to optimize by passing region/entity_ids/selection and reusing geometry_cache_token after detect_parts. Explicitly states to avoid calling create_dimension_* repeatedly.

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

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

Annotations already mark it as destructive (destructiveHint: true) and non-readonly. The description adds context: batch creation in one Undo group and accepted dimension types/forms. No contradictions, but it doesn't cover failure modes or authorization needs, so a 3 is appropriate.

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?

Two succinct sentences: first states the core function, second provides usage guidance and parameter hints. No redundant words; every sentence earns its place.

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 complexity (nested objects, output schema exists), the description covers creation purpose, batch nature, and dimension types. It lacks details on output or structure, but output schema likely fills gaps. Sibling context is minimal but sufficient.

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%, so description must compensate. It explains that data.dimensions accepts specific types (linear, diameter, etc.) in two forms, which adds value. However, it does not detail the object structure or include_screenshot semantics, so it is only partially helpful.

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 tool's purpose: 'Create two or more dimensions in one request and one Undo group.' It specifies the verb (create), resource (dimensions), and distinguishes from siblings by emphasizing batch creation and Undo group atomicity.

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 explicitly advises: 'Use this instead of repeatedly calling annotation.create_dimension_*.' This provides clear when-to-use guidance. It implies not to use for single dimensions but does not list all alternatives; a bit more explicit exclusion would earn a 5.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds value by explaining clustering, return format (part_1, part_2...), and cache reuse behavior. No contradictions.

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?

Two sentences with zero fluff: first sentence defines purpose, second provides critical performance guidance. Every word earns its place.

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?

The description covers core functionality and performance rules, but omits parameter semantics and lacks detail on what the indexed preview includes. Output schema exists, so return values are documented elsewhere, but parameter info is missing.

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 description coverage is 0%, and the description does not mention any parameter (data, include_preview). It fails to add meaning beyond the schema, leaving users to infer purpose and constraints of the two parameters.

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 tool 'Cluster Model Space geometry and return part_1, part_2... with an indexed preview', specifying the verb (cluster and return) and resource (independent drawing parts). This distinguishes it from sibling tools like annotation_audit_dimensions or drawing, which have different purposes.

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?

Provides explicit performance rules: 'pass region, entity_ids, or selection='current' whenever possible' and 'reuse geometry_cache_token together with target_part_id...'. While no explicit when-not-to-use or alternatives, the guidance on efficient use is clear and actionable.

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

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

The description claims 'Create or revise' which implies mutation, but annotations declare readOnlyHint=true, a direct contradiction. This undermines transparency.

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 one sentence but too vague to be effective. It fails to convey essential information concisely.

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 0% schema coverage, no parameter explanations, and a contradictory description, the tool definition is incomplete for an agent to use correctly.

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%. The description does not explain the 'data' or 'include_preview' parameters, leaving the agent without meaningful guidance.

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 it creates or revises a plan and explicitly says no AutoCAD entity is created, but 'D1/D2... plan' is vague. It somewhat distinguishes from siblings that deal with dimensions.

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 on when to use this tool versus alternatives like annotation_auto_dimension or annotation_batch_create_dimensions.

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

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

The description aligns with the destructiveHint annotation by mentioning removal and fixing. However, it adds no additional behavioral details such as what exactly gets destroyed, required permissions, or rate limits. The title provides some context but is not part of the description.

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 single concise sentence with no unnecessary words or repetition. It is appropriately front-loaded.

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 that the tool has an output schema, no required parameters, and a destructive hint, the description is too sparse. It does not explain what kind of data is expected, how the screenshot parameter affects behavior, or what the output looks like. The title and annotations provide some context, but the description itself is incomplete.

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 description provides no information about the parameters (data, include_screenshot). With 0% schema description coverage, the description fails to add any meaning beyond the bare schema 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 clearly states the tool's purpose: removing duplicates and fixing issues related to safe layer/style/lane from a fresh audit. However, it does not differentiate itself from sibling tools like annotation_audit_dimensions or annotation_plan_dimensions, which might also deal with layout issues.

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 on when to use this tool versus alternatives. The phrase 'from a fresh audit' implies it is used after an audit, but this is not explicit, and there is no mention of when not to use it.

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

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

With readOnlyHint=false, the tool is already marked as potentially mutating, and the description adds meaningful behavioral details: save mentions QSAVE fallback, undo/redo state operations, and purge targets unused objects. It does not disclose destructive side effects (e.g., purge deleting data permanently), but the per-operation explanations go well beyond the bare annotation.

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 tightly formatted bullet list with no filler. Each line adds one distinct operation plus a brief explanation and data hint, and the overall purpose is front-loaded in the first line.

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?

For a ten-operation dispatcher, the description covers each operation's function and relevant data requirements, and an output schema exists to cover return values. The main gap is the unexplained `include_screenshot` parameter, which prevents the description from being fully complete.

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 description coverage is 0%, so the description is the only documentation of valid `operation` values and `data` structures. It lists all operations and gives per-operation data hints such as `data: {path}` for open and `data: {names: [...]}` for get_variables. However, the `include_screenshot` parameter is never mentioned, leaving one parameter undocumented.

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 "Drawing file management" and then enumerates ten distinct operations, each with a verb and a resource (e.g., "create — Create a new empty drawing," "plot_pdf — Plot to PDF"). This makes the dispatcher's purpose and each subcommand unambiguous. Although sibling tools are not referenced, the operations are clearly scoped to whole-drawing management, distinguishing it from entity/layer/block tools.

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 operation list implicitly tells an agent when to use this tool (e.g., when saving or opening a drawing), but there are no explicit when-not-to-use statements or pointers to siblings like entity, layer, or block. Usage context is conveyed indirectly through the operation names, not through explicit routing guidance.

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

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

The description reveals that operations mutate the drawing by creating layers, inserting symbols, and connecting equipment, which is consistent with the readOnlyHint=false annotation. It does not disclose prerequisites such as whether setup_layers must be called first, coordinate system expectations, or the effect of include_screenshot. It adds operation-level behavior but not deeper behavioral context.

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 tight, consistently formatted operation list with no filler. The domain statement is front-loaded, and every line adds a distinct operation or data shape. It is an excellent model of concise reference documentation.

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?

For a multi-operation dispatch tool, the description covers all operation names and their data payloads, and an output schema exists so return-value documentation is not essential. It is slightly incomplete around the include_screenshot parameter and setup ordering, but otherwise sufficient for correct invocation.

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 description coverage is 0%, but the description lists the expected data keys for each operation, including optional fields marked with '?'. This substantially compensates for the generic schema. The only structured parameter not explained is include_screenshot, which prevents a 5.

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 opening phrase 'P&ID drawing with CTO symbol library' plus the enumerated operations (setup_layers, insert_symbol, draw_process_line, etc.) makes the tool's purpose concrete. It stops short of a clean single verb+resource statement and does not explicitly contrast with sibling drawing/layer tools, so it earns 4 rather than 5.

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 operation list implies when to use this tool, such as when inserting P&ID symbols or drawing process lines. However, it never explicitly states when to prefer this tool over sibling tools like drawing, layer, or block, and it gives no exclusions. Guidance is implied rather than explicit.

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