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

With no annotations, the description discloses approval behavior and the need for manager approval on first use. However, it does not clarify whether reports are removed from the original agent or if the action is reversible, which is important for a mutation tool.

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 brief and front-loaded with the main purpose. The approval note in brackets adds necessary context but could be more concise. Overall efficient.

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?

Given no output schema, the description lacks information about the result of reassignment (e.g., success message, whether reports are copied or moved) and does not mention reversibility. Still, it covers the core action and trigger phrases sufficiently.

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% with descriptions for all parameters. The tool description adds minimal value beyond the schema, mainly through examples. Baseline of 3 is appropriate as the schema already adequately describes each parameter.

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 clearly states the tool reassigns all scheduled reports from one agent to another, provides example user utterances, and identifies use cases like deactivating an agent or hiring a replacement. It distinguishes from sibling tools by being specific to report reassignment.

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?

Explicitly describes when to use (when user says 'reassign reports', 'transfer reports to [agent]', etc.) and after deactivating an agent or hiring a replacement. Does not explicitly exclude alternative scenarios but provides clear context.

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