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

Annotations already declare the safe read-only profile, so the description only needs to add context beyond that. It usefully discloses pagination behavior (50 per page, capped at 200, offset to continue) and that only loaded/fetched pages are listed, which is real behavioral detail not present in the annotations.

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?

Three sentences, front-loaded with the return content, then pagination mechanics, then the usage cue. Efficient and well ordered, with no filler.

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 read-only list tool with no output schema, the description covers what is returned (titles and URLs), pagination, and the selection cue, while annotations cover safety. An agent has enough to call it correctly; only explicit sibling routing is missing.

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 0%, so the description carries the burden and does add meaning: limit is the per-call count (max 200) and offset retrieves the continuation. It doesn't mention the default of 50 explicitly as a default or the minimum of 1, but the core semantics of both parameters are conveyed.

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+resource: returns a list of pages on esprit-delasse.com with title and URL. The scope (loaded/fetched pages) is concrete, though sibling differentiation is only implied via 'find what pages exist / when search fails' rather than naming search or search_pages.

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?

Gives a usage context ('when you want to know what pages exist, or when searching and can't find something'), which hints that search is tried first. However, it never names the alternative tools (search, search_pages, site_overview) or states when this is the wrong choice, so guidance remains implicit.

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