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

Annotations already declare readOnly/openWorld=false/destructive=false, so the description's real added value is the auth behavior: an unsigned connection triggers FlareWarden sign-in, which an agent needs to anticipate. It also previews the response composition. It does not address the idempotentHint=false oddity on what is a read, and gives no pagination or truncation behavior for the incident/attention lists.

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?

Front-loaded with the use case, then the auth prerequisite, then the return inventory, then exclusions — a sensible ordering with no filler sentences. The return inventory is a long comma-list but each item corresponds to distinct content an agent must know.

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 carries the return-value burden by enumerating what comes back and in what order (attention list worst-first, at most three suggestions). Combined with the sign-in prerequisite and the exclusions, nothing material for correct invocation is missing.

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 and there is nothing for the description to disambiguate. No argument-related guidance is needed.

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?

Names a concrete verb and resource (account overview) and enumerates the specific payload: identity/plan/role/permissions, monitor capacity, sites by status, open incidents with confirmation, worst-first attention list, and up to three suggestions. It distinguishes itself from siblings by explicitly excluding check_service_status and the no-account case, so an agent can pick it without opening another schema.

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 concrete trigger conditions ('starting any conversation about the user's own account', 'what is wrong / needs attention / what to set up next') plus two explicit exclusions with a named alternative ('use check_service_status' for another company's service status). When-to-use, when-not-to-use, and the alternative are all present.

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