get_manual

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

No annotations are provided, so the description carries the full burden. It does disclose the essential behavior — a zero-parameter read that returns reference content, therefore inherently non-destructive — but says nothing about return format, length, or whether the content is static or context-dependent. That omission is notable for a tool whose entire value is the payload.

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 front-loaded sentence that leads with what is returned before the topic enumeration. Every clause earns its place by telling the agent what content to expect. Slightly list-heavy, but no filler or redundancy.

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, no-output-schema retrieval tool, the description supplies the one thing the agent needs: what knowledge it will obtain. The lack of any hint about return size or format is the main residual gap, but the topic list makes the tool's purpose sufficiently clear to call.

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 takes zero parameters, so there is nothing for the description to disambiguate; the 4 baseline applies. The description makes clear it is invoked without arguments, matching the empty object schema with 100% coverage.

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+resource: it returns a built-in authoring manual, and enumerates the topics covered (locator syntax, element actions, waits, tab management, capture, CDP recipes, launch customization). This clearly distinguishes it from siblings like run_cdp or run_drission_code, which execute rather than document. It stops short of a 5 only because the manual's scope beyond the listed topics is undefined.

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?

No when-to-use guidance, no prerequisites, and no reference to the sibling tools whose DSL it presumably documents. The agent must infer on its own that this is a reference to consult before calling run_drission_code or run_cdp. Nothing states when-not to call it or whether it is cheap to call repeatedly.

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