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

Goes well beyond readOnlyHint=false by disclosing owner-only permission, the one-time-code email flow, member capabilities, team size cap, pending invite replacement that invalidates earlier codes, a 2-per-day email limit, and key replacement behavior for existing members.

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?

Front-loads the core purpose, then adds dense but useful behavioral constraints. Some sentences are awkward and parenthetical-heavy, but almost every sentence carries operational information rather than 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?

For a mutation tool with no output schema and minimal annotations, it supplies the key context an agent needs: permissions, limits, replacement side effects, and edge cases for existing members and cross-team membership.

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 50%, and the company parameter already has a schema description. The description implies the email is the invitee address, but it does not explain the optional company parameter or the multi-company selection case, leaving a meaningful gap.

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?

Starts with a specific verb and resource: inviting a colleague to the company's RepuTend account by email, with owner-only scope. It is clearly distinguishable from siblings such as remove_member, list_team, and redeem_invite.

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?

Explains owner-only use and operational constraints, including pending-invite replacement, team size limits, daily email limits, and existing-member behavior. It points to list_team for size, but does not explicitly route to redeem_invite or remove_member as alternatives.

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