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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to explain what comes back—which it does for each mode: listings with short descriptions and contained endpoints, or an OpenAPI file with method, url, headers, query params, path variables, request body example and sample responses. No pagination or depth-limit caveats are mentioned.

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?

Front-loaded with the core model, then three parallel 'Call it with...' sentences that map cleanly to the modes. The repeated 'Call it with `path` set to...' phrasing is slightly verbose but each sentence carries distinct information, so nothing is wasted.

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?

With no output schema present, the description must explain return values—and it does so for all three modes. Combined with the annotations covering safety and a fully documented single parameter, an agent has everything needed to call this correctly on the first try.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the semantic effect of each path form—a module/page link yields a listing, a '.openapi.yml' link yields an OpenAPI document, omission yields the top level. That behavioral mapping of parameter values is genuinely value-adding.

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 (browse) and resource (Liliphant API docs) with an explicit traversal model ('one level at a time'). It distinguishes itself from siblings like search_liliphant_docs and call_any_api_of_liliphant by framing itself as the navigation/index layer rather than a search or call tool.

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 concrete invocation guidance for three modes: no argument for the top level, a module/page link for a listing, and a '.openapi.yml' link for endpoint detail. 'Fetch only the level you need' is a clear efficiency instruction. It doesn't explicitly say when to prefer this over search_liliphant_docs, which keeps it from a 5.

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