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

Annotations already declare non-read-only, idempotent, destructive, closed-world, so the safety floor is set; the description adds real context beyond that — the account/workspace prerequisite, the role-based permission model, and the fallback behaviour when a role is insufficient. What it leaves unstated is the destructiveHint implication: whether assigning over an existing owner replaces the prior assignee, and that a Slack notification is apparently dispatched (only hinted at via "whether they heard in Slack").

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?

Front-loaded with the trigger scenario and closed with prerequisites and exclusions, so every sentence carries information. The one flaw is density: "The work is the bid call while a tender waits in Watching or Qualifying, or a sprint step, the next one unless named" is a run-on that takes a second pass to parse.

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 an output schema present, return values needn't be spelled out, and the description still summarizes the response (who has the work, Slack acknowledgement). Prerequisites, permissions, defaults, alternatives and an example are all covered; only the reassignment/overwrite behaviour implied by destructiveHint=true is missing.

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%, but the description still earns credit for explaining the default semantics of the omitted `task` param ("the next one unless named") and for tying the work types to tender state (bid call while a tender waits in Watching or Qualifying). The inline example JSON shows the interplay of tender_reference, person and task in a way the schema does not.

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 opening sentence names a specific verb and resource — giving (or taking) a piece of bid work to a person — and anchors it in an explicit user utterance ("give the Bristol bid call to Sam"). It also names the two nearest siblings it is NOT (update_bid_sprint, record_bid_call), so an agent can discriminate it without opening a schema.

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?

It states the trigger condition, the scope of "work" (bid call while in Watching/Qualifying, or a sprint step defaulting to the next one unless named), the escalation path when the person's role can't do the work ("the answer says who can: ask the user before choosing one"), and explicit exclusions routing to update_bid_sprint and record_bid_call.

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