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

'Read-only' adds nothing beyond the readOnlyHint annotation, and the tool adds the return shape { total, pages: [...] }. However, 'Returns (json)' is contradictory with the response_format default of 'markdown' in the schema, so the description misrepresents the default response format. No pagination/ordering caveats are disclosed.

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 one compact sentence with the action and key fields front-loated, plus a terse read-only note. 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 optional-parameter, well-annotated tool, the description supplies the necessary return-shape and field list because there is no output schema. It is slightly incomplere because it omits the markdown/json default caveat and does not route to get_wiki_page for a single page, though the schema mitigates the format issue.

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 carries all parameter information (100% coverage): response_format enum, default, and meaning are fully documented in the input schema. The description contributes no additional parameter sematics and its 'Returns (json)' wording is ambiguous against the default, but the schema itself is sufficient.

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 uses a specific verb+resource ('List all Onchain Agent wiki pages') and enumerates the returned fields (slug, title, keyword, summary, last_updated). It clearly distinguishes from sibling get_wiki_page (single-page fetch) and list_categories (different entity) by emphasizing 'all 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?

It implies use when you need an inventory/overview of wiki pages, but it never explicitly says when to choose this over get_wiki_page or list_categories. No alternates, exclusions, or preconditions are given; the intended usage must be inferred from the name and title.

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