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

No annotations provided, so description carries full burden. It states the output fields (path, title, section) and implies completeness ('every page'). However, it does not disclose behavior like ordering, rate limits, or whether the list is paginated. For a simple list tool with no params, this is adequate but not thorough.

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 concise sentences that front-load the action. Every word is useful. No extraneous information.

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 parameters, no output schema, and no annotations, the description provides sufficient context for a simple enumeration tool. It tells what it returns and suggests initial usage. Could optionally mention output format or size, but not required.

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?

No parameters exist, and schema description coverage is 100%. Baseline is 3 per rubric. Description adds no parameter meaning beyond the empty schema, which is fine since there are none.

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?

Clearly states the tool lists every Medius documentation page with path, title, section. Verb 'List' and resource 'Medius documentation page' are specific. Distinguishes from siblings like 'get_page' (single page) and 'search' (content search) by emphasizing full enumeration.

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 says 'Start here to see what the docs cover', guiding the agent to use this first for overview. Does not explicitly mention when not to use (e.g., if you need detailed content, use 'get_page' or 'search'), but the start-here advice implies sequencing.

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