beel_docs_list

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

Annotations already communicate readOnlyHint and openWorldHint, and the description adds the important behavioral clarification that the returned text is documentation content rather than instructions to follow. This goes beyond the annotations and helps prevent misuse of returned data.

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 two sentences with no fluff. The core purpose is front-loaded, and the safety-relevant clarification is placed second without distracting from the main point.

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 zero-parameter listing tool, the description is complete: it states what is returned, clarifies its nature, and requires no additional context. No output schema is present, but the return value is adequately described in prose.

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 tool has zero parameters, so there are no parameter semantics to document. The description fully covers what the tool does and returns, meeting the baseline for a no-parameter tool.

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 clearly states a specific verb ('List') and resource ('BeeL documentation pages'), and specifies the output (titles and URLs). It does not explicitly differentiate itself from the sibling tools beel_docs_get and beel_docs_search, though the verb 'list' suggests the distinction.

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 tool is used to discover available documentation pages, but it provides no explicit when-to-use guidance or mention of alternatives such as beel_docs_get or beel_docs_search. The added warning that returned text is documentation, not instructions, is a useful usage note but does not address tool selection.

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