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

With zero annotations, the description carries the full burden and delivers: immediate org membership with board access via role inheritance, no personal namespace, no login capability, auto-issued first API key returned in plainKey that is never shown again, and the owner/admin permission requirement. These are exactly the irreversible and authorization facts an agent needs before invoking.

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?

Four dense sentences that each carry non-redundant information, with the core action front-loaded in sentence one. The parenthetical loadings ('User type=\'agent\'', 'board access via role inheritance') add a little friction but no filler.

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?

No output schema exists, and the description compensates by disclosing the key return artifact (plainKey, single-display) as well as membership, namespace, login, and permission behavior. Nothing material an agent needs to call this mutation correctly is missing.

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 all four parameters are already documented with constraints and the role enum semantics. The description adds only marginal param-level meaning ('board access via role inheritance'), so the baseline 3 applies.

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 ('Create a non-human agent account (User type=\'agent\')') scoped to an organization namespace, which clearly separates it from human-membership siblings like add_board_member and invite_board_member. An agent can identify the target entity type without opening the 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?

Gives a clear activation context (provisioning a non-human agent identity) plus the prerequisite 'Requires organization owner/admin.' It never explicitly names the alternative path for adding humans, so there are no exclusions, but the context for when this tool applies is unambiguous.

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