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

Annotations already declare readOnlyHint=true, so safety is covered by structured data. The description goes beyond that by characterizing cost ("cheap") and by enumerating exactly what comes back, which tells the agent this is a low-side-effect diagnostic rather than a data-mutating call. No auth-scope or rate-limit detail, so not a 5.

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 plus a trailing endpoint reference, with the resource and the field list front-loaded and the practical rationale second. No filler, no restatement of the title.

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 compensates by listing the fields the call returns, and the zero-parameter schema needs no explanation. An agent has everything required to decide whether to invoke it and what to expect.

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 there are no parameter semantics to document — baseline 4 per the rubric. The description instead spends its words on the return payload, which is the relevant information for a no-arg call.

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 connected Checkfront account's company configuration) and enumerates the actual fields returned — name, URL, plan, currency, timezone, locale, date/time formats. It is cleanly distinguishable from every sibling, none of which touch account-level settings.

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?

Explicitly frames the use case: "A cheap way to confirm the host and credentials work." That resolves the main ambiguity an agent would have (why call this at all?) and implies it is a low-cost connectivity/auth probe. It stops short of naming alternatives or when-not-to-use conditions, so it does not reach 5.

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