rhino_drawing_export_pdf

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

The annotations already declare readOnlyHint=false, indicating a state-changing operation, and the description does not contradict that. Beyond that, the description adds only 'bridge only' as a small operational constraint. It does not disclose that the tool writes a file to disk, whether existing files are overwritten, or what occurs when the specified sheet does not exist.

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 front-loaded sentence with zero filler — the verb and target appear immediately. This is appropriately concise, though the brevity comes at the cost of a second sentence that could carry important operational details without harming readability.

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 file-exporting operation with four parameters (two required), a one-line description is insufficient even though the output schema exists so return values need not be explained. Missing context includes what 'bridge only' means in practice, the side-effect of writing an output file, prerequisites (a sheet must exist), and overwrite behavior. The schema documents structure, not operational semantics.

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?

Per context signals, schema description coverage is 0%, so the description must compensate for undocumented parameters. It only loosely maps to sheet_id via 'a sheet' and says nothing about dpi, the output path requirement, or the doc_id handle (despite the schema containing brief descriptions for path and doc_id). The description does not meaningfully help an agent understand the parameter contract.

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 (Export), a specific resource (a sheet), and the output format (PDF), which is confirmed by the annotation title 'Export Sheet to PDF'. It is not a tautology and the 'bridge only' qualifier adds a scope constraint. It does not explicitly distinguish itself from sibling export tools (rhino_export_obj, rhino_export_step, rhino_render_to_file), but the sheet-to-PDF resource mapping makes the purpose reasonably clear.

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?

There is no guidance about when to use this tool versus alternatives like rhino_render_to_file, rhino_view_capture_to_file, or the various model export tools. The only constraint, 'bridge only', describes an environment/availability restriction rather than a usage selection criterion, leaving the agent without direction on choosing the right export tool.

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