Get Cluster

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

With readOnlyHint=true already declaring the safe-read profile, the description still adds real value: the full return shape, that role ARNs and secret credentials are never exposed, and that auth requires a user access token plus organization membership. It does not cover rate limits or error behavior, keeping it just below top marks.

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?

Bold section headers front-load purpose and returns, and every block earns its place given the missing output schema. The Returns paragraph is dense but justified by the need to describe the response without a schema.

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?

No output schema exists, so the description proactively covers return values, credential non-exposure, auth requirements, and the decision context relative to list-clusters. Nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100% and both parameters are documented there ('Dedicated cluster ID returned by list-clusters', 'Organization containing the cluster'). The description adds no format or syntax detail beyond the schema, so the baseline 3 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, and scope ('Get one RawTree dedicated cluster and its current lifecycle status'), which cleanly separates it from the sibling list-clusters. An agent can distinguish it without opening the schema.

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 'When to use' block gives three concrete triggers plus an explicit anti-condition ('You already have a cluster ID and do not need the full organization cluster list'), routing the agent away from list-clusters.

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