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

With no annotations, the description must disclose behavioral traits. It states it returns a one-time invite link for new users and is owner-only, but it does not describe side effects of role changes, whether changes are reversible, or error handling. The description carries the burden and only partially fulfills it.

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 efficient, front-loading the core action, then providing role definitions and the owner restriction. Each sentence adds value without excessive verbosity.

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 tool with three parameters and no output schema, the description covers roles, return value for new users, and permission. However, it does not explain behavior for role changes (e.g., whether an invite link is also returned) or mention the workspace parameter's importance in multi-workspace scenarios, which is left to the schema.

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 100%, but the description adds significant meaning to the role parameter by defining each enum value (owner, member, guest) with concrete implications. This goes beyond the schema's simple 'Default member.'

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 the tool adds a person or changes their role, using a specific verb and resource. It distinguishes from siblings like users_invite by explicitly covering role changes, though it does not name the sibling directly.

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?

The description mentions 'Owners only' as a permission constraint but provides no guidance on when to use this tool versus alternatives like users_invite or users_remove. There is no explicit when/when-not guidance.

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