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

The description adds genuine context beyond annotations by disclosing the account:manage permission requirement for invites, something annotations cannot express. It does not say what happens when inviting an existing member, whether invites are idempotent, or how pending invitations differ from members despite openWorldHint=true implying external side effects such as sending email.

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 compact clauses, one per action, with the authorization caveat placed last where it applies. No filler, no repetition of the title, and the action verb is front-loaded so an agent can scan the right path immediately.

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 tool mixing a read action and a write action, the description covers both action branches and the auth prerequisite, which is adequate given there is no output schema to explain. It remains thin on failure modes and on how the list results are scoped (workspace-wide? pending only?), which matters for an open-world tool.

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?

With 0% schema description coverage, the description carries the full burden and mostly meets it: it maps action=invite to the email and role parameters, and enumerates the valid roles. It omits that role is not formally required by the schema and what default applies when it is omitted, so a small gap remains.

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 names both discrete actions with their resources — listing members and pending invitations, and inviting an email with a role. It is a specific verb+resource statement rather than a restatement of the name. It stops short of distinguishing itself from the sibling list_members, which appears to cover the same list capability.

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?

Usage is implied by the action names, and the one real prerequisite — account:manage for inviting — is stated explicitly. However, there is no guidance on when to use action list versus the sibling list_members tool, and no note on when not to invite (e.g. already-existing members), leaving selection partly to inference.

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