Fetch a Lichtblick documentation page

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

Annotations already establish readOnlyHint=true, so safety is covered. The description goes beyond that by disclosing the return format — the full markdown body, not a summary or snippet — which matters for context budgeting. It still omits size/truncation behavior and whether an invalid path errors gracefully.

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?

A single sentence that front-loads the return type and resource before the input forms. No filler, no restatement of the title.

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 carries responsibility for return values and does address them ('full markdown'). For a one-parameter read-only fetch tool that is nearly complete; only edge behavior on an invalid path or oversized document is unaddressed.

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 100% on the single 'path' parameter, so the baseline is 3. The description adds real value by stating where path values originate (docs_search/docs_list) and by mentioning URL as an accepted form, though that URL option is not reflected in the schema and could confuse an agent.

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 and resource — 'Returns the full markdown of a documentation page' — and specifies the two input forms (path or URL). The parenthetical '(from docs_search/docs_list)' implicitly positions this as the retrieval step after discovery, but it never explicitly contrasts itself with siblings like extension_api_get, which fetches a different resource type.

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?

The description implies the workflow by naming docs_search/docs_list as the source of paths, which tells an agent to discover first and fetch second. However, it gives no explicit when-to-use guidance against extension_api_get/extension_api_list, which cover a distinct lookup surface, and no prerequisites or exclusions.

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