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

Adds substantial behavior beyond the annotations (which only give the generic write/non-destructive profile): the write is a PENDING suggestion, applies only on accept, requires an active org member, and the result carries a `load` breakdown. The last point is especially valuable because there is no output schema.

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-loads purpose, mechanism, and the usage condition before the extended `load` paragraph. The `load` detail is justified given the absent output schema, but it is verbose and could be tightened without losing meaning.

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 compensates by enumerating what the `load` result contains and noting it also travels in the suggestion. Purpose, prerequisite, usage condition, and return content are all covered for a 3-parameter mutation tool.

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%, so the schema already documents all three parameters, setting the baseline at 3. The description reinforces that the target must be an active org member and that `reason` is shown to the reviewer, but adds no format/syntax detail the schema lacks.

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 and resource ('Propose assigning a task to a teammate') and immediately clarifies the mechanism: writes a PENDING suggestion that only assigns on accept. This cleanly distinguishes it from the sibling assign_task, which performs the assignment directly.

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?

Explicit when-to-use guidance: 'Use when you can identify the right owner but want human confirmation before assigning.' That condition implicitly routes the agent away from direct assignment, but it never names the alternative sibling (assign_task) explicitly, so the routing is inferred rather than spelled out.

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