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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds scope (only the signed-in user's Projects) and payload shape (Projects plus active Site details), which annotations cannot convey.

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 front-loaded sentence with zero filler: verb, resource, scope, return content, and purpose all in one clause. Nothing to trim and nothing reordered for clarity.

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, no output schema, and safe annotations, the description covers what an agent needs: what is listed, whose data, and why. Return-format detail (pagination, project ID field names) is absent but low-stakes for an enumerating tool of this kind.

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 schema baseline is 4. Nothing in the description contradicts or obscures that; the only mild gap is that it never says the call is unfiltered/global.

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 the signed-in user's Projects') plus the payload ('active Site details'), so the agent knows exactly what it gets back. It does not, however, distinguish itself from the sibling tool 'list_projects', which could plausibly return the same resource.

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?

The clause 'so the user can choose a target without knowing an internal Project ID' implies the calling context (discovering a Project ID before a dependent call), which is useful. But there is no explicit when-to-use/when-not guidance and no reference to the near-duplicate sibling 'list_projects' to disambiguate.

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