Is this project actually working?

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

Annotations already establish it is a safe read, but the description adds real behavioral context beyond them: the auth requirement ('Requires the project.read grant') and the return contract ('Each check comes back with the one action that fixes it'), which matters because there is no output schema. Rate limits or response format details are absent, keeping it short of a 5.

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?

Three sentences, front-loaded with purpose then usage then auth requirement, with no filler. The middle sentence is long and does double duty, but every sentence earns its place.

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?

For a single-parameter diagnostic with no output schema, the description covers what it checks, when to call it, the auth requirement, and what it returns (a fixing action per check). Nothing an agent needs to invoke 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?

Only one parameter, and schema description coverage is 100% (the schema documents the prj_... format). The description adds nothing about the parameter, so the baseline of 3 for a fully covered schema is appropriate.

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 ('Checks whether a project is really connected to a website') and then enumerates the three concrete sub-checks: key presence, whether a site has ever used it, and whether views arrive from rendering pages. This is clearly a diagnostic tool, distinct from siblings like get_integration_guide or get_content_analytics, so an agent can select it without opening the 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 explicit triggering conditions: 'ALWAYS call this after wiring up an integration, and always when somebody says views or analytics are zero.' It even explains the discriminating scenario (a site that fetches content but reports nothing), which tells the agent when this is the ONLY right tool.

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