list_pages

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

The description 'List all wiki pages' aligns with readOnlyHint=true, but adds no additional behavioral context beyond the annotations. For a simple listing, this is adequate but not insightful regarding pagination or other traits.

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 extremely concise and front-loaded, containing one sentence with no superfluous words.

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 simple listing tool with one parameter, the description covers the main purpose. However, it omits potential details like pagination or whether it returns all pages (including unpublished), but overall it is sufficiently complete given the low complexity.

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?

With 100% schema description coverage for the single parameter course_id, the description adds no extra meaning. 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 description clearly states it lists all wiki pages in a course, using the specific verb 'list' and resource 'wiki pages'. This distinguishes it from siblings like get_page (single page), create_page, delete_page, etc.

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?

The description implies usage for listing all wiki pages but does not explicitly state when to use this tool versus alternatives (e.g., get_page for a specific page) or when not to use it. No exclusions or context provided.

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