Comment on a todo or idea

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

Annotations already declare this is a non-destructive, non-idempotent write (readOnlyHint=false, idempotentHint=false), and the description adds no behavioral detail on top: it says nothing about duplicate comments on repeat calls, whether edits/deletes are possible afterward, or what the call returns. The only added text (target_kind values, agent_id required) is schema content, not behavior.

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 short sentences, front-loaded with the action and routing rationale. Reasonably tight, though the closing "agent_id required" restates a required field already visible in the schema and earns little.

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 simple write tool with annotations covering the safety profile and no output schema, the description is adequate but thin: it omits how to obtain or format target_id and whether repeated calls duplicate the comment (relevant given idempotentHint=false). Those gaps matter more than return-value documentation, which is excused here.

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 only 25%, and the description repeats what the schema already says (target_kind enum values, agent_id required) rather than filling the gap. target_id — a required parameter with no schema description — is left completely undefined, as is the 4000-char body limit already noted only in 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 ("Adds a comment to a Boardroom todo or idea") and implicitly distinguishes itself from the top-level message tool by contrasting scoped discussion against a Boardroom message. The sibling (post_message) is described but not named directly, so differentiation is not fully explicit.

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?

"Use for discussion that belongs scoped to that item rather than as a top-level Boardroom message" gives a clear selection condition against the alternative. No negative case is given (e.g., what target_kind values are invalid or when commenting is the wrong escalation path), so it stops short of a full when/when-not treatment.

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