box_desktop

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

The description discloses that the URL is 'secret-bearing' and instructs 'Never log the full URL,' adding important behavioral context beyond the readOnlyHint and openWorldHint annotations. It does not contradict 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 extremely concise with two short sentences. The first sentence states purpose, and the second provides a critical safety instruction. No word is wasted.

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?

With three parameters, low schema coverage, and no output schema, the description is too brief to be complete. It omits parameter explanations, return value details, and usage context, making it inadequate for full agent comprehension.

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 only 33% (only boxId is described). The description mentions no parameters (vnc, publicAccess) and fails to explain their meaning or effect, leaving the agent without necessary parameter semantics.

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 purpose with a specific verb ('Get') and resource ('desktop/noVNC URL'). It distinguishes itself from siblings by specifying a URL for desktop access, which is unique among the listed box_* tools.

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 guidance is provided on when to use this tool versus alternatives. The description only states what it does and adds a logging caution, but offers no context about typical use cases or exclusions.

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