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

readOnlyHint=true already covers the safety profile, so the description's marginal burden is low. It adds useful framing that the call is cheap and credential-scoped, but says nothing about failure modes (e.g. what happens with invalid credentials) or response shape beyond three field names.

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 sentences, zero waste, front-loaded with the verb+resource followed by the value proposition and the underlying API route. Every clause earns its place.

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-param read with annotations covering safety and a described return payload, this is nearly complete. A brief note on auth failure behavior or whether region affects later calls would close the remaining gap.

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?

Zero parameters, so baseline is 4. The description correctly implies the org is inferred from credentials rather than passed as an argument, which is meaningful given the API route shows a {orgSlug} path variable.

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 ('Fetch the OfficeRnD organization') and enumerates the returned fields (name, slug, region), which no sibling does. An agent can distinguish this org-lookup from member/booking/ticket tools immediately.

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?

Provides one implied use case ('a cheap way to confirm the setup works') but does not name alternatives or state when not to use it. Adequate but thin for a routing decision among 19 siblings.

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