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

readOnlyHint=true already establishes a safe read. The description adds useful context beyond the annotation: the call is 'cheap' (an implicit cost/rate consideration) and serves as a credential sanity check, which is a genuine behavioral trait an agent wouldn't infer from the annotations alone.

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 compact sentences plus an endpoint reference, with the returned-resource identity front-loaded. Every clause earns its place; nothing is repeated from the title or annotations.

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, and the description compensates by naming the fields returned, so an agent knows what to expect. The only minor gap is that it does not describe the response's shape or nesting, but for a zero-argument account lookup this is close to 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, so schema semantics are a non-issue and the baseline is 4. The description correctly adds no parameter discussion because none exists.

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 (get the account summary for the key's church) and enumerates the returned fields: name, subdomain, status, timezone, country/currency. This clearly separates it from every sibling, which all deal with people, events, tags, forms or funds rather than the account 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 an explicit use case: 'A cheap way to confirm BREEZE_SUBDOMAIN and BREEZE_API_KEY are right.' That tells the agent when to reach for it, though it stops short of naming an alternative tool or stating when not to call it (there isn't really a competing sibling here).

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