Create dry-run publish plan

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds 'deterministic' and 'never modifies or plots it', which goes beyond the annotations by specifying the exact behavioral guarantee. This is valuable additional 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, front-loaded sentence that immediately states the action and safety guarantee. There is zero redundancy or extraneous detail.

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 simple tool (1 parameter), rich annotations, and presence of an output schema, the description adequately covers all necessary context: what it does, the single-file scope, determinism, and lack of side effects. No gaps are apparent.

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 100% for the single 'path' parameter, with a description that explains the path policy. The tool description adds minimal extra meaning ('one DWG') that is already implied by the tool's purpose, so the baseline of 3 is appropriate.

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 function with specific verbs ('Inspect', 'return') and a specific resource ('one DWG'). It explicitly distinguishes this from batch operations by using 'one' and from actual publishing by stating it is a 'dry-run plan' and 'never modifies or plots'.

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 context is clear: use for a single DWG to get a deterministic dry-run plan without side effects. While no explicit alternatives are named, the sibling tool 'create_batch_publish_plans' is implicitly contrasted via 'one DWG', providing adequate usage context.

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