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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description goes beyond them by disclosing what each entry carries (current role and effective MCP capabilities) and by imposing a presentation rule about projectId, which is real behavioral context an agent would otherwise lack.

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, zero filler. Scope comes first, then the output-handling instruction, so the agent gets the actionable constraint before it ever sees the results.

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 an output schema present, return-value detail is already covered, and the description supplies the one thing the schema cannot: how to treat projectId downstream. Nothing needed to select or invoke this call 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?

The tool takes zero parameters, so there is nothing for the description to explain about inputs; the baseline of 4 applies. It correctly avoids restating the empty schema.

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?

The description uses a specific verb and resource ("List standard PaperDock projects accessible to the connected account") and disambiguates it from the file/comment/chat siblings, which all operate within a project. The qualifier "standard" hints at other project types but never names them, so a small ambiguity remains.

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?

It tells the agent how to use the output — "Use projectId only for subsequent tool calls and do not show it unless explicitly requested" — which effectively positions this as the entry-point call that supplies IDs for the rest of the toolset. No sibling alternative exists to route against, so the absence of explicit exclusions is not a real gap.

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