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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds that results are paged, which is genuine behavioral context, but says nothing about the shape of returned sites, how to detect the last page, or rate/limit behavior.

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 short fragments with zero redundancy, and the resource identity is front-loaded before the pagination note. It leans toward terseness rather than padding, so it earns credit for efficiency rather than being penalized.

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 one-parameter, read-only list tool this is minimally viable: the agent knows what it lists and that it paginates. With no output schema, the description should have said what a site record contains and how pagination terminates, which it omits.

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 is a single optional parameter and the schema documents it fully (1-based, max 100000, 100 results per page, use next_page from the previous reply). With 100% schema coverage the schema does the work, and the description contributes only the word 'Paged', so 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?

The description names the resource ('Sites (job locations)') and scopes it to the 'Project Management view', which is more specific than the title. However, it is a bare noun phrase with no verb, and it does not distinguish this tool from the very similar sibling gocanvas_list_locations or from gocanvas_list_projects, leaving the agent to guess which list of locations is intended.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite gocanvas_list_locations and gocanvas_list_projects existing. The only usage signal is the trailing 'Paged.', which implies iteration but not selection criteria.

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