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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: a separate team:read consent is required and module authority follows registered requirements, and it discloses that responses carry exact expectedRevision and newInviteId tokens — valuable for chaining into the prepare_* tools. However, it never says what happens on missing consent or how the revision token is consumed, so it stops short of full disclosure.

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 first sentence is front-loaded and dense with useful scope, but the text is a run-on that bundles read scope, authorization requirements, exclusions and invitation-role assignment guidance into one block. The final clause about assigning owner/manager/employee roles and post-acceptance operator membership does not belong in a read tool's description and costs clarity.

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?

With no output schema and no parameters, the description carries the burden of describing the return payload, and it does so by enumerating members, roles, active/inactive access, the four invitation states, and the revision/invite identifiers. It omits any notion of result shape, ordering or pagination, but for a parameterless read tool the coverage is adequate.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to document and the schema is closed (additionalProperties false). The mentioned expectedRevision and newInviteId are response fields, not inputs, so they neither help nor hurt this dimension.

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 opening clause gives a specific verb and resource (read the current tenant's team members, roles, access states and invitation states), which is far more than a restatement of the name. It does not name a sibling such as prepare_team_access_change to contrast against, and the trailing sentence about invite roles (owner/manager/employee) and operator membership role describes assignment behavior rather than reading, which slightly muddies what the tool actually returns.

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 sets boundaries — no other tenants' users, no credentials, no arbitrary entitlement modification — which implicitly routes mutation work elsewhere, but it never names the sibling tools (prepare_team_access_change, prepare_team_invitation) or states the condition that selects them. Usage is thus inferable rather than explicit, leaving the agent to guess whether this tool can also initiate changes.

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