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

With no annotations, the description carries the full behavioral burden and does well: it discloses that membership is immediate, that no invitation is created or accepted, that owner/admin permission is required, and that the owner role cannot be granted. It omits edge behavior such as what happens if the username is already a member or unknown, which is the only meaningful gap for a state-mutating tool.

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?

Two tight sentences: purpose and mechanism first, permission and role constraints second. No filler, no restating of the name, and every clause carries information the caller needs.

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 three-parameter mutation tool with no output schema and no annotations, the description supplies the essential context: immediate grant, no invitation, permission level, and role ceiling. Only the duplicate/invalid-username behavior is left unstated, which is a minor rather than blocking gap.

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%, with board_id, username, and the role enum all documented inline, so the schema already does the heavy lifting. The description only reinforces the role constraint ('cannot create or assign the owner role'), adding marginal value beyond what the schema states.

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 ('add a user directly to a board') and immediately clarifies the mechanism ('they become a member immediately, with no invitation to accept'), which implicitly separates it from invite_board_member among the siblings. An agent can distinguish it from the invitation/ownership siblings without opening any schema.

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?

Tells the agent when to use it ('add a user directly... no invitation to accept') and names the access restriction ('Owner/admin only'), which is real usage context. It stops short of naming invite_board_member explicitly as the alternative path, so selection between the two still requires a small inference.

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