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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: the sort order, the explicit exclusion of HTML, and the exact fields returned (_id, name, widgets read by name, url). It stops short of mentioning pagination or result limits, which is the only gap for a list endpoint.

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 dense sentences with the core operation front-loaded, and the alternative tools packed into a trailing sentence rather than scattered. The nested appositive for url ('the page where a signed-in project member opens it') is slightly ornate for the value it adds.

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?

There is no output schema, so the description must carry the return shape, and it does enumerate the returned fields and the HTML exclusion. The missing piece is any statement about result volume or pagination, which an agent listing a large project would need.

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 100% and the single projectId parameter is fully documented in the schema, including its provenance from fastero_list_projects. The description adds nothing parameter-specific, so the baseline 3 applies.

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 a project's hosted pages) plus two distinguishing qualifiers: sorted most-recently-changed-first and returned without HTML. It also names the sibling tools it is not (get_page, show_page), so an agent can separate it from the other page tools without opening any 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?

Explicitly routes the agent: get_page 'reads one's HTML and recent errors' and show_page 'shows one live in the conversation', leaving list as the choice when you only need the inventory. The parenthetical that _id is 'the pageId other page tools take' also tells the agent when to call this first as a discovery step.

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