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

Annotations already declare the write/non-destructive/idempotent profile, and the description adds the critical behavior they cannot express: the rule is staged on the Team rules page and nothing follows it until the user approves it there. Permission, rate-limit and error behavior are left unstated, keeping this short of a 5.

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?

Two sentences, no padding, with the deferred-approval constraint placed where it will be read. The opening clause 'Keeps one rule the user's agent proposed from the user's correction' is slightly dense but still parses on one pass.

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 three-required-parameter write tool with no output schema, the description covers what the tool does with the input and the lifecycle state the record lands in. Only the post-call result (confirmation or identifier) is unaddressed, which is a minor gap given annotations cover idempotency.

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?

All three parameters carry full schema descriptions including max lengths, so the schema does the heavy lifting. The description's 'why it exists and where it applies' merely restates the 'why' and 'where' fields rather than adding syntax or format guidance, which is the expected baseline at 100% coverage.

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 verb 'keeps' plus the resource 'one rule' and the scope 'from the user's correction' make the operation identifiable, and the 'waits on the rules page' clause signals it is a staging/proposal write rather than an activation. It stops short of naming the sibling it differs from, so an agent must infer how propose-team-rule relates to set-team-rules or get-team-rules.

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 trigger context is explicit: a rule that came out of a user correction is what belongs here, and the description makes clear the tool is not for applying rules that are already live. It offers no explicit when-not or named alternative, but the pending-approval framing gives an agent enough to decide.

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