help

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It states that the tool returns 'comprehensive documentation' but does not detail the output format, potential size, or that it is a read-only operation. For a help tool, the behavior is inherently non-mutating, but the description could have explicitly said so.

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, well-structured sentence that is front-loaded with the core action. It avoids any wasted words while still conveying the tool's scope ('all reasoning tools functions').

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 tool with no output schema or annotations, the description fully covers the tool's purpose and scope. 'Comprehensive documentation for all reasoning tools functions' is sufficient for an agent to know what to expect and when to invoke it.

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 the baseline score is 4. The description does not need to explain parameter semantics since there are none. The schema coverage is trivially complete, and the description adds no unnecessary details.

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 the tool 'Get comprehensive documentation for all reasoning tools functions' with a specific verb (get) and resource (documentation for all reasoning tools functions). It is immediately distinguishable from sibling tools like boolean_evaluate or date_calculate, which perform reasoning operations rather than provide documentation.

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 implicitly communicates when to use the tool: whenever the agent needs documentation for reasoning tools. It doesn't explicitly mention exclusions or alternatives, but as a meta-tool for help, the usage context is clear. No sibling tool serves the same documentation purpose, so the lack of explicit alternatives is not a gap.

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