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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds real context: the account is resolved implicitly from the API key (explaining why there are no parameters) and the underlying endpoint GET /accounts/info is disclosed, which is beyond what the annotations provide.

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?

One sentence enumerating the payload plus a short endpoint reference, with the resource identified up front. Nothing is padded and every clause carries information.

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?

With no output schema and no parameters, the description carries the burden of telling the agent what comes back, and it does so by listing the fields. It stops short of noting behavior on invalid or missing API keys, but for a zero-argument read that is a minor 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?

The tool takes zero parameters, so the baseline is 4 under the rubric. The description correctly reinforces this by framing the account as implicit ("behind the API key"), leaving no ambiguity about whether an identifier must be supplied.

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?

The description gives a specific verb and resource ("The Encharge account behind the API key") and enumerates exactly which fields come back (id, name, site, status, timezone, people count, active services). That is far more concrete than a restatement of the title, though it never explicitly positions itself against siblings like encharge_get_people or encharge_list_segments.

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?

Usage is only implied: an agent can infer this is the call to make when it needs account-level metadata, but there is no statement of when to use it, when not to, or what alternative exists. No prerequisites or auth requirements beyond the passing mention of "behind the API key" are spelled out.

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