card-addComment

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

The description only says 'adds a comment' without disclosing behavioral traits like whether comments are appended, if authentication is needed, or any side effects. No annotations are provided to compensate.

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?

The description is one sentence and is very concise. It is front-loaded but could benefit from slightly more detail without becoming verbose. No unnecessary 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?

Given the tool has 2 parameters (one nested), no output schema, and no annotations, the description is insufficient. It does not explain how to use the parameters effectively or what the result of adding a comment looks like.

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 description coverage is 50% (only requestBody has a description). The tool description does not add any additional meaning for the cardPublicId parameter or clarify the requestBody structure beyond what the schema provides.

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 description clearly states 'Adds a comment to a card' with a specific verb and resource. It distinguishes from sibling tools like card-deleteComment and card-updateComment. However, it is brief and could include more context about the card identifier.

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?

No guidance is provided on when to use this tool versus alternatives such as card-addOrRemoveLabel or card-addOrRemoveMember. There is no mention of prerequisites or exclusions.

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