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

Annotations declare readOnlyHint=true and the description reinforces the same read-only nature while adding the binding scope ("this token or session is bound to") and the exact data surface returned. It doesn't add auth requirements or rate limits, but for a safe zero-arg read with annotation coverage already present, the field disclosure is meaningful added context.

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-loaded with what the resource is and what it returns, followed by the usage rule and a terse "Read-only" close. The parenthetical field enumeration is dense but every item earns its place as return-value context; only the CLI twin reference is arguably 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?

With no output schema and no parameters, the description carries the full burden of explaining the return payload, and it does so by listing the returned fields. Combined with the read-only cue and the usage condition, an agent has everything needed to call it correctly.

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 there are no parameter semantics to explain; baseline is 4. The schema is empty and requires nothing, and the description correctly implies no arguments are needed by framing the org as inferred from the session/token.

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?

Names a specific resource (the organisation bound to the token/session) and enumerates exactly what it returns: id, name, slug, creation time, member and service-principal counts, and org-wide settings. It is clearly distinguishable from siblings like list_organisation_members, list_organisation_roles, and list_organisation_variables, which fetch sub-collections rather than the org itself.

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?

Gives explicit routing guidance: "Use this first when a request says 'my organisation' or 'our account' and nothing else names it." That states both the triggering condition and the fallback situation, which is exactly what an agent needs to disambiguate against the many organisation-scoped list/set tools.

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