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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds valuable behavioral context: it is a browser-lane render, it returns only bounded title/headings/snippets, and it costs 3 MESH/call. It also explicitly states it does not access private memory, vault, or estate context, which is important behavioral disclosure beyond the annotations.

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 compact and front-loaded: it states the action, the resource, the output bound, and the privacy exclusion in two sentences. The cost note and tool tag are appended without bloat. Every sentence earns its place.

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 single-parameter tool with no output schema, the description covers the key facts: what it renders, what it returns, what it excludes, and the cost. It does not specify the exact input payload structure for the render (e.g., URL field name), but the schema's 100% coverage and the example pattern partially compensate. The privacy exclusion is especially valuable given the sibling set includes memory and estate-related tools.

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 description coverage is 100%, so the schema already documents the single 'input' parameter. The description adds the capability-specific payload example pattern but does not detail the exact shape for this tool's render payload. With 100% coverage, baseline 3 is appropriate; the description adds some context but the schema carries the heavy lifting.

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 ('Render'), a specific resource ('a public HTTPS page through DevDesk Scout's browser lane'), and a clear scope ('bounded title/headings/snippets only'). It also explicitly excludes private context ('No private memory, vault, or estate context'), which distinguishes it from sibling tools like devdesk-cog-public-ask and devdesk-sandbox-public-probe.

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 clearly implies when to use this tool: when you need a public page rendered with bounded output. It also states what it is not for ('No private memory, vault, or estate context'), which helps an agent avoid using it for private-context tasks. However, it does not explicitly name alternative tools or state when-not-to-use conditions beyond the privacy exclusion.

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