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

Annotations only establish readOnlyHint=true, but the description adds real behavioral detail the annotations don't carry: zero-based paging and the next_page-until-null termination protocol, which is essential to avoid missing data. It stops short of noting rate limits or ordering of results, so not 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 short sentences, no filler, and the core scoping constraint plus pagination protocol are front-loaded before the alternative-tool pointer. 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 two-parameter read-only list tool this covers the essentials an agent needs: what it returns (a page), how to advance, and where to go for filters. With no output schema, a brief note on result ordering or what a project record contains would have closed the remaining gap.

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 coverage is 100%, so both parameters (page, limit) are already fully documented with defaults, minimums and maximums. The description restates the zero-based origin and introduces next_page, which is a response field rather than an input parameter, so it adds only marginal semantic value.

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 one page of Hub Planner projects") and scopes the result set explicitly to a single page. It also distinguishes itself from the sibling search tool, so an agent can tell list-projects from search-projects without opening a 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 concrete usage context: start at page 0 and follow next_page until null, and use the search tool for filtered results. The hedge "where available" weakens the routing instruction slightly, and it never mentions when to prefer hubplanner_get_project for a single known project.

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