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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true) by disclosing the real consequence — a message other people will see — and the consent precondition, which no annotation conveys. It also explains that the webhook is never an argument and that a missing webhook produces an informative failure rather than a silent no-op.

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 sentences, each load-bearing: destination, side-effect/consent warning, and the webhook/failure behavior. The safety-critical warning is front-loaded rather than buried at the end.

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 one-parameter mutation tool with no output schema, the description covers everything an agent needs: destination, consent requirement, external configuration, and failure semantics. Annotations cover the safety profile and the description covers behavior.

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%, so the single 'text' parameter is already documented, but the description adds two things the schema cannot: the webhook URL is deliberately not a parameter, and the note is rendered as the chat would show it. That negative/contextual clarification is genuine added value over the baseline.

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 precise verb (posts), resource (a finished standup note) and destination (the chat webhook saved on the connect page, naming Slack/Discord/Google Chat). An agent can separate this from get_standup_data or get_note_instructions purely on this sentence.

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 constrains use: 'only call it on a note the user has agreed to send,' plus the concrete failure path when no webhook is saved. It lacks an explicit pointer to the sibling that produces the note content, but the context is otherwise unambiguous.

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