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

readOnlyHint=true already establishes the safety profile, so the description only needs to add context — and it does, by naming the exact fields returned (name, slug, region) and framing the call as a lightweight connectivity check. It stops short of noting auth/token failure behavior, which would be the natural additional detail for a setup-verification call.

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?

Three short sentences, front-loaded with what is fetched and what comes back, then the use case, then the underlying endpoint. Nothing is redundant and the endpoint reference aids traceability without bloating the text.

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 parameterless read with no output schema, the description compensates by listing the returned fields and the call's purpose. Nothing else is required for an agent to invoke 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?

With zero parameters the baseline is 4. The description adds a genuinely useful implication — the org is derived from the supplied credentials, not passed in (the endpoint's {orgSlug} is resolved internally) — which preempts an agent searching for an org parameter that does not exist.

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 (Fetch) and resource (the OfficeRnD organization tied to the current credentials) and enumerates the returned fields — name, slug, region. It is trivially distinguishable from siblings like get_member or get_booking, which are also reads but of different resources.

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?

'A cheap way to confirm the setup works' gives a concrete when-to-use scenario, which is a real usage signal rather than filler. No explicit when-not or named alternative is offered, but for a credential-scoped org lookup there is no competing sibling to route against.

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