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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds valuable non-obvious behavior: adding a label triggers the board's 'label added' rules, as in the app. It does not cover auth needs, board/label scoping, or response behavior, but it adds real context beyond annotations.

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?

One efficient sentence with no waste. It is front-loaded with the operation, though parameter/format details are absent rather than over-explained.

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 3-param mutation tool with no output schema and 0% schema description coverage, the description should explain add/remove semantics and side effects. It does disclose the rule-triggering side effect, which is valuable, but leaves parameter meaning and scoping incomplete.

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 0%, so the schema documents none of the three parameters. The description mentions adding and removing labels implicitly referencing 'add' and 'remove', but provides no syntax, format, or semantics for the arrays or the required cardId, leaving the burden unmet.

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 (Adds/removes) and resource (labels of the task's board on a task). Distinguishes from create_label/delete_label by operating on a task's label assignments, though it does not explicitly name a sibling alternative.

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?

Implied usage is clear from the description, but there is no explicit when-to-use/when-not guidance, no mention of alternatives, and no stated prerequisites beyond the required cardId.

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