listPages

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

No annotations are provided, so the description carries the full burden. The description only states it lists all pages, but does not disclose whether the operation is read-only, what data is returned (e.g., names, IDs), or any side effects. For a simple list tool, minimal disclosure is acceptable, but it still lacks key behavioral context.

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 a single sentence with no unnecessary words. It is front-loaded with the action and resource. Every part 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?

Given no output schema and no annotations, the description should at least hint at what is returned (e.g., page names or IDs). It does not, leaving the agent to guess. With many sibling tools, more context would help the agent decide when to use this tool. It is incomplete for a tool with no structured output documentation.

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 no parameters, so the schema coverage is 100% trivially. The description adds no parameter semantics beyond the schema, but this is acceptable as there are none to describe. Baseline score of 3 is appropriate.

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 tool name and description clearly state it lists all pages in a Sketch document. The verb 'list' and resource 'pages' are specific, though the description could be more detailed about what a 'page' is in this context. It distinguishes from siblings like 'getPageStructure' which likely returns more detailed info.

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 guidance is provided on when to use this tool versus alternatives. Sibling tools like 'listNodesByPage' or 'getPageStructure' could be confused with this one, and the description does not mention when to prefer this tool or what prerequisites exist.

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