rhino_drawing_export_pdf

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

The description does not disclose behavioral traits beyond exporting a PDF. Annotations show readOnlyHint=false, indicating side effects, but the description lacks details such as file overwriting behavior, required permissions, or any limitations. The 'bridge only' note is a usage constraint, not behavior.

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 front-loads the primary action. It contains no unnecessary words, making it efficient. However, the brevity may sacrifice completeness.

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?

Given the tool has multiple parameters (dpi, doc_id, path) and a non-read-only action, the description is insufficient. It does not explain the bridge context, output behavior, or parameter nuances. While an output schema exists (per context signals), its absence from the description leaves gaps.

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 description provides no information about parameters. The input schema has descriptions for 'path' and 'doc_id' but not for 'sheet_id.' With 0% schema description coverage overall, the agent has minimal guidance beyond parameter names. The description should clarify parameter roles, especially 'sheet_id' and 'doc_id.'

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 exports a sheet to PDF and specifies 'bridge only,' distinguishing it from other export tools. The verb 'export' and resource 'sheet' provide a specific, actionable purpose.

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 phrase 'bridge only' gives some context on when to use this tool, implying it is intended for use when connected via a bridge. However, it does not explicitly state when not to use it or mention alternative tools like other export functions.

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