beel_docs_get

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds behavioral context by specifying it fetches the 'full' page with 'all its sections', which is not in the annotations. It does not disclose potential failure modes, but for a read-only docs fetcher this is sufficient.

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 a single, focused sentence stating the core action and scope, followed by a practical usage tip. No wasted words, and the key information is front-loaded.

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 tool with one parameter, no output schema, and read-only annotations, the description covers the essential aspects: what it does, when to use it, and how to pass the parameter (via the schema). The behavior of returning a full page is clear, and no critical details are missing for an agent to call it correctly.

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%, with the parameter described as 'Page title or a distinctive part of it.' The description adds only illustrative examples ('Invoice types', 'Regime keys') that mirror the schema. Since the schema already defines the semantics, the description provides marginal value, warranting the baseline score of 3.

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 states a specific verb ('fetch') and resource ('full documentation page by title'), and clarifies it returns all sections. It also gives concrete examples ('Invoice types', 'Regime keys') and explicitly situates itself after beel_docs_list or beel_docs_search, distinguishing it from those siblings.

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?

Explicitly instructs when to use this tool: 'Use after beel_docs_list or beel_docs_search to read a page in full.' This clearly indicates the workflow — list/search to find a page, then this tool to get its full content. No exclusions are needed given the sibling set.

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