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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description doesn't need to restate that. It adds a valuable behavioral detail: 'Optional source_stage ... returns 409 when stale', disclosing a concurrency control behavior not covered by annotations. It does not mention other side effects like cascading deletions or behavior on missing item_ids, but the provided detail is useful beyond the structured data.

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, front-loading the primary action and then adding the optional parameter behavior. Every word earns its place; there is no fluff or repetition. The structure is efficient and clear.

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 delete operation with 5 parameters and nested objects, the description covers the core action and the optional concurrency check. It does not explain what a successful response looks like (no output schema exists), but that is not required. It also doesn't mention prerequisites like the draft existing or the anchors being present, but the destructive and idempotent annotations cover the safety profile. Overall, it is fairly complete for the operation's complexity.

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 explain parameters. It explicitly mentions 'by item id' for the item_ids parameter and describes the source_stage object with its stage and version fields, including the 409 behavior. It does not detail the resource.id parameter, but that is implied as the draft identifier from the schema pattern and title. Overall, it compensates reasonably for the missing schema descriptions.

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?

States a specific verb ('Delete'), a specific resource ('behavioral-anchor entries for draft items'), and the key selector ('by item id'). This clearly distinguishes it from sibling tools like update_anchors or generate_anchors based on the action alone. The title 'Delete draft scorecard anchors' reinforces the purpose.

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 implies usage by its action verb and resource but provides no explicit guidance on when to choose this tool over alternatives (e.g., when to use delete_questions vs delete_anchors). It does not state exclusions such as 'only for draft items, not published plans', although the title hints at drafts. No comparison with sibling delete tools is given, so an agent must infer context.

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