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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses important behavioral traits: 'Deleted/moved tickets remain visible; unknown estimates are not zero' and the permission requirement 'Requires tickets:read.' These are meaningful details an agent needs to correctly interpret the comparison results. There is no contradiction with annotations.

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 two sentences with no filler. The main action is front-loaded, followed directly by the two key behavioral caveats and the permission requirement. Every clause 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?

For a simple single-parameter read-only tool with rich annotations and no output schema, the description covers the purpose, ownership constraint, behavioral caveats, and required permission. It does not describe the output format or return shape, but that is not essential given the low complexity and the clarity of the comparison action.

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 input schema has 0% description coverage and one required parameter, baseline_id. The description compensates by indicating that the baseline must be 'owned', which adds meaning to baseline_id beyond its name and UUID type. While not an explicit parameter description, the single obvious parameter and the 'owned baseline' qualifier are sufficient.

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 a specific verb and resource: 'Compare an owned baseline with current scope, estimates and completion.' This clearly distinguishes it from sibling tools like get_scope_baseline or list_scope_baselines, which retrieve rather than compare, and from diff_portfolio_snapshots, which targets snapshots instead of baselines. The phrase 'owned baseline' adds a precise ownership scope.

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 provides useful context by specifying that the baseline must be 'owned' and that access requires 'tickets:read', but it does not explicitly state when to choose this tool over siblings or when not to use it. The use case is implied rather than directly contrasted with alternatives such as get_scope_baseline or diff_portfolio_snapshots.

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