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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description still adds real value by disclosing the authorization constraint (owner/admin-level key) and that page-scoped keys are rejected. It stops short of mentioning pagination or response shape, but the added auth context is meaningful beyond the annotations.

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 short sentences that front-load what the tool returns, followed by the access condition. Every clause carries information; the phrasing 'not a key held to one page' is a touch telegraphic but still compact and content-bearing.

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 zero-parameter read tool with no output schema, the description supplies both the fields returned (people, roles, invitations, seats) and the key-permission requirement, and the annotations cover the read-only nature. It is close to complete; only return formatting/pagination details are absent, and those are minor here.

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 schema has nothing to document and the baseline for a parameter-free definition is 4. Nothing in the description misleads about inputs, and no parameter guidance is needed.

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 enumerates the resource and its contents concretely — team members with roles, open invitations, seats — so an agent knows exactly what is returned. It does not explicitly name a sibling it might be confused with, but none of the sibling tools (get_app, get_dashboard, list_views, etc.) competes for the same lookup, so differentiation is implicit and adequate.

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?

It provides an access precondition (owner/admin keys only, and not a key scoped to a single page), which governs whether the call can succeed. However, it gives no when-to-use guidance against alternatives or any positive trigger context, so usage is only implied.

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