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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered by structured data. The description adds genuine value beyond that by disclosing the payload contents, including dynamic state like "the setup steps still to do, and any scan in progress," which tells the agent the response reflects live workspace state. It stops short of describing ordering, pagination, or the empty-workspace case.

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, front-loaded with the primary action and followed by the routing rule. The field enumeration in sentence one is long, but it substitutes for the absent output schema, so the density is earned rather than padding.

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 full burden of explaining the return value, and it does so field by field while also establishing the tool's role as the entry point for the rest of the site toolset. Nothing an agent needs to select or invoke this tool 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 there is nothing for the description to disambiguate and the baseline applies. The description correctly makes no parameter claims and instead spends its words on output semantics, which is the right allocation for a no-arg 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 a specific verb and resource ("List every tracked site (project) of the workspace") and immediately enumerates what comes back (id, visibility, share of answers, prompt counts, competitors, share of voice, setup steps, scan in progress). It also names the sibling it is not (get_dashboard) for a different reporting need, so an agent can distinguish it without opening any 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 an explicit ordering rule — "Call it first: every other site tool needs the projectId it returns" — which is exactly the prerequisite context an agent needs before touching update_project, list_prompts, etc. It also routes the alternative case ("For one site's full weekly report use get_dashboard") to the correct sibling.

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