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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the invitee receives a notification and must accept, and that owner/admin permission is required, but it omits what happens on duplicate invitations, whether invitations expire, what gets created, and error 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?

The definition is three short sentences and front-loads the core action, with permission details preserved at the end. 'Use this command to' is slightly redundant filler, but overall it is efficient and well-structured.

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 moderate-complexity mutation tool with rich schema coverage but no annotations and no output schema, the description covers purpose, permission, and acceptance workflow. It still leaves notable gaps around invitation lifecycle, duplicate handling, cancellation, and response 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 description coverage is 100%, so the schema already documents board_id, username, and role with enum and default details. The description adds no parameter meaning beyond that structured data, making the baseline 3 appropriate.

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 states a specific verb and resource: 'invite a user to a board.' The added note that the invitee 'must accept' distinguishes this from a direct-add operation like add_board_member, but it does not explicitly name the sibling tool or clarify the boundary in so many words.

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?

It provides a permission prerequisite ('Owner/admin only') and implies the invitation workflow, but gives no explicit when-to-use versus alternatives guidance. An agent must infer that this is for pending invitations rather than immediate membership changes.

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