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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description supplements this with meaningful behavior: the default sort order (newest first), the exact row fields, the pagination envelope fields, and how tagPath scoping behaves. No contradiction exists between description and 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?

The description is three sentences with no filler. It front-loads the core purpose, then provides return-shape and scoping details, then closes with a practical sorting tip. Every sentence 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?

There is no output schema, so the description appropriately documents the return shape: same rows as search_wiki plus a pagination envelope with totalPages, hasMore, and nextPage. It covers filtering, sorting, and pagination context well enough for an agent to invoke the tool correctly without additional lookup.

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?

The schema covers all four parameters (100%), so the baseline is solid. The description adds value beyond the schema by explaining that tagPath values should come from get_categories, that omitting tagPath walks the whole wiki, and that sort=title produces an A-Z listing. Page and pageSize are not elaborated further, but their schema defaults are 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 and resource: browsing the wiki by tag path, listing every page under a branch. It distinguishes itself from search_wiki by contrasting tag-path browsing with keyword browsing and even references the shared row format with search_wiki.

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 explicitly frames when to use this tool: when browsing by tag path rather than keyword. It also gives concrete guidance to pass a tagPath from get_categories to stay inside a branch, omit tagPath for the whole wiki, and use title sort for an A-Z pass, which effectively routes an agent to the right use case.

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