help

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

With no annotations provided, the description carries the full burden. It states the tool 'gets comprehensive documentation', which implies a read-only, informational behavior. However, it does not disclose additional details such as the format of the documentation or any potential side effects. The description is minimally transparent but not contradictory.

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 concise sentence that is front-loaded with the main action. Every word earns its place, and there is no unnecessary information. This is exemplary conciseness.

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 help tool with no parameters and no output schema, the description is fairly complete. It clearly states what the tool does and implies the scope (vision functions). However, it could be slightly enhanced by explicitly mentioning that it covers the sibling tools, but the context signals already provide those siblings, so the description is adequate.

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 0 parameters, so the schema is trivially complete. The baseline for 0-parameter tools is 4, and the description does not need to add parameter information. It simply focuses on the tool's purpose.

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's function: 'Get comprehensive documentation for all vision functions'. It uses a specific verb ('Get') and a clear resource ('documentation for all vision functions'), distinguishing it from sibling tools that perform vision actions rather than providing help.

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 for obtaining help about vision functions, but it doesn't explicitly state when to use it or mention any alternatives. For example, it doesn't say 'use this when you need details about vision_screenshot'. Usage is inferred from the name and description rather than explicitly guided.

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