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

The annotations already declare readOnlyHint=true and destructiveHint=false, setting a low bar. The description reinforces this by using 'List' and explicitly states what information is returned (role and effective MCP capabilities). It does not mention any side effects or restrictions beyond the output guidance, but given the read-only annotations, this is sufficient.

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?

The description is two sentences, front-loaded with the primary action and resource, followed by a concise note on handling the output. Every sentence adds value; there is no fluff or redundant phrasing.

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 parameterless listing operation, the description is complete. It specifies the resource type, the additional output fields (role and capabilities), and gives a practical usage note. The output schema (not shown but present) would cover structural details, so no further context is needed.

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?

There are zero parameters, and schema coverage is 100% (empty object). The description does not need to explain any parameters, and the absence of param details is not a gap. The mention of projectId being for subsequent calls is about output semantics, not input parameters.

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 verb 'List' clearly indicates a read-only operation, and the resource 'PaperDock projects' is specific. The description also mentions including the account's role and effective MCP capabilities, providing additional detail about the output, which makes the purpose unambiguous.

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 description gives practical guidance on how to handle the returned projectId ('use projectId only for subsequent tool calls and do not show it unless explicitly requested'). It does not explicitly contrast with sibling tools like list_files or list_comments, but the scope is clear enough from the resource type, and the guidance on projectId is useful for downstream usage.

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