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

Annotations already establish the safe read-only profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds genuinely non-obvious behavior: it explicitly discloses what is NOT returned (a report's private link, recipients' addresses), which is important data-availability context an agent cannot infer from annotations.

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?

A single dense sentence plus a short exclusion clause, front-loaded with what is returned. Every clause earns its place, though the packed parenthetical field lists make it slightly list-like rather than neatly structured.

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 parameters and no output schema, the description compensates by enumerating the returned fields and the fields deliberately withheld, so an agent knows both shape and limits of the result. Nothing needed to call it correctly 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?

Zero parameters, so the baseline is 4 per the rubric. The description correctly adds no parameter detail and instead documents the returned data fields, which is the right use of space for a no-input tool.

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 precisely what is retrieved — public status pages (title, public link, sites, on/off) and monthly client reports per site — with the exact fields involved. No sibling tool covers status pages or client reports, so the agent can identify this tool's scope immediately.

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: 'Edited in the dashboard's Agency page' hints that this tool reads while editing happens elsewhere, but there is no explicit when-to-use/when-not or named alternative. A read-only retrieval tool is self-evidently for inspection, so this is adequate but thin.

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