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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds non-obvious side-effect scope ("neither deletes nor creates a tracker issue") and implies revision-exact/optimistic concurrency semantics, which the annotations do not convey; it still omits what happens to the proposal itself and what occurs on a stale revision.

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?

A single front-loaded sentence with a clarifying clause and no filler. It is efficient, though the phrasing "Rejects exact pending revision" is slightly elliptical and could read as a fragment.

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 four required parameters, a nested request object, full schema coverage, and an output schema covering return values, the description supplies purpose plus side-effect scope, which is close to sufficient. The remaining gap is the pre-call/error condition for a stale or non-pending revision.

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 100% and every parameter is documented in the schema, including `data` as the expected revision sourced from engineering_proposals. The description reinforces the "exact revision" meaning of `expected_revision` but adds no format or failure-mode detail beyond the schema; baseline 3 applies.

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 names a specific verb and resource ("Rejects ... revision") and scopes it to a pending proposal revision, which is enough for an agent to know what the tool does. It stops short of naming its counterpart (engineering_approve) or distinguishing itself from siblings like engineering_edit or engineering_reconcile.

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?

"Pending revision" implies the precondition that an open proposal must exist, and the schema points to engineering_proposals as the source of `expected_revision`. However, there is no explicit guidance on when to reject versus approve, edit, or reconcile, so the agent must infer the routing from sibling names.

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