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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful visibility constraint that only published/public records appear. It says nothing about pagination, ordering, or result size, which for a cursor-paginated list tool is a real gap.

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?

Nine words, front-loaded, zero filler. However it is a bare noun phrase with no verb, so it reads as a label rather than a statement of what the call returns, which slightly undercuts its efficiency.

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 paginated, open-world discovery tool with two undocumented parameters and no output schema, the description should say at minimum how paging works and what a result contains. Annotations cover safety but cannot cover pagination semantics, and the description leaves that entirely unaddressed.

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?

Schema description coverage is 0% and the description never mentions either parameter. 'limit' and 'cursor' are only inferable from their types and constraints (max 50, UUID format); the description does not explain paging behavior, default page size, or how to resume with a cursor.

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 fragment states the resource precisely: published, public projects that are actively seeking help, explicitly excluding private drafts. It lacks an explicit verb (relying on the tool name 'list_projects') and never names a sibling like list_opportunities or list_problems, so differentiation is only partial.

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?

'no private drafts' implies a negative condition (don't use this to see your own unpublished work, use create_project_draft or a draft-scoped tool instead), but no alternative is named. There is no guidance on when to prefer list_projects over list_opportunities or list_problems, leaving selection to inference.

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