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

Goes well beyond the annotations: it states the reminder actually SENDS a message over email/Slack/SMS, that delivery is irreversible, and that cancel only affects unfired reminders. Those are exactly the consequences an agent needs before invoking a destructiveHint=true 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?

Three tight sentences, front-loaded with the action, then the consequence, then the guardrail. The middle clause runs long with two joined ideas (irreversibility and cancel scope) but every sentence carries information.

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 7-parameter mutation with an output schema and annotations, the description covers creation, irreversibility, and recipient scope. Multi-workspace token behavior lives only in the schema, which is acceptable but is the one area an agent might still stumble on.

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 already 100%, so the baseline is 3; the description earns more by explaining the semantics of omitting `recipients` (send to self) and `channels` (recipient preference) and by framing recipients as real people who will each receive a message. Tenant-slug and document-slug behavior is left to the schema.

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 ("Create a one-off reminder") and scopes it to "one or more tenant members". The word "one-off" implicitly separates it from kb_reminders_create_schedule, but the sibling is never named outright, so the agent must infer the split.

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?

Gives an explicit gating rule: "Create one only when the user asked for it, addressed to the people the user named." That is real when-to-use guidance plus an exclusion on recipient targeting, though it never points to kb_reminders_create_schedule for recurring cases.

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