compare_schedules

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond that: activities match on P6 Activity ID or MS Project Unique ID, the section parameter controls full-list output, and the report includes many specific comparison categories. It does not disclose edge-case behavior, but the annotations lower the burden.

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 front-loaded with the core purpose, which is good. However, the long enumeration of comparison sections is written as one dense run-on sentence and would be far more scannable as bullets or shorter sentences. The material is relevant but not optimally structured.

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 no output schema, the description does a solid job of conveying both the tool's selection context and its output content: it lists all major comparison sections and the activity matching key. It omits the meaning of limit and the project parameters and does not describe the return format, but the core selection/invocation information is largely present.

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 must compensate, but it only explains the section parameter ('Pass section=<name> for one section's full list') and the ID-matching rule. It does not clarify limit, previous_path, current_path, current_project, or previous_project semantics, leaving five of six parameters effectively 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 a specific verb and resource: 'Update-to-update comparison of two versions of a schedule (previous vs current update).' This clearly distinguishes it from sibling tools like baseline_variance, which would compare against a baseline rather than another update. The subsequent list of report sections reinforces what the tool produces.

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 gives clear context for when the tool is appropriate: comparing two schedule updates rather than, say, a baseline-to-current comparison. It does not explicitly name alternatives or state when not to use it, so it falls short of a full 5, but the usage context is unambiguous.

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