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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond annotations: the response is authorization-dependent, since 'Only an owner or an admin sees pending invitations' — an agent must not treat missing invitations as absence of invitations. It stops short of saying what else may be hidden.

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 tight sentences with no filler: the first front-loads the scope and payload, the second delivers the one conditional behavior an agent most needs. Nothing is repeated from the schema or annotations.

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, the description correctly carries the return-value burden by enumerating the fields returned, and it flags the permission-dependent visibility of invitations. It is close to complete for a one-parameter read tool; only the alternative read tools for the same org remain unrouted.

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?

There is a single parameter with 100% schema description coverage, including the provenance hint 'Organization id from list_organizations.' The description adds no additional parameter meaning, so the baseline of 3 applies — the schema does all the work.

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?

States a specific verb and resource ('Show one organization') and enumerates the fields returned (members/roles, Pro seats, seats in use, invitations, settings, flow count), which separates it from list_organizations and the narrower get_org_usage/get_org_security/get_org_audit_log siblings. It never names a sibling explicitly, so the differentiation is inferred from the field list rather than stated.

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 only implied: 'Show one organization' with an org_id from list_organizations suggests a detail-view call after listing. There is no explicit when-to-use vs. get_org_usage/get_org_security/get_org_audit_log guidance and no exclusion criteria, so the agent must infer routing from field overlap.

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