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

readOnlyHint=true is already in annotations, but the description adds real value: required permissions (kube_access.manage, kube_access.policy, kube_access.elevate), the meaning of is_configured=false (defaults apply), and the fact that a pending proposal plus its apply_url may also be returned. That is meaningful context beyond the annotation.

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-loads the resource identity, then packs the returned fields into one dense but informative sentence, then ends with permissions and read-only status. Slightly heavy in the middle enumeration but each clause carries information an agent would otherwise lack.

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?

There is no output schema, so the description correctly carries the burden of describing return contents (policy fields, is_configured semantics, pending proposal with apply_url) and access requirements. Only the absence of explicit sibling-routing guidance keeps it from being fully complete.

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 and schema coverage is 100%, so there is nothing for the description to compensate for. Baseline for 0 params applies.

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+resource (retrieves the organisation cluster access policy) and enumerates exactly what that policy contains (creator role, highest grantable role, max grant duration, reason threshold). However it does not directly differentiate itself from nearby siblings like propose_cluster_access_policy or get_service_cluster_policy; the reference to the `ankra org access-policy get` CLI twin is helpful but is not a sibling tool.

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?

There is no when-to-use or when-not-to-use guidance. The reader is told it requires kube_access.manage/policy/elevate but is never told when to call this versus propose_cluster_access_policy (which likely relates to the pending proposal returned here). Usage must be inferred entirely.

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