upload_large_format_drawing

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

Without annotations, the description carries the full burden. It discloses the ability to skip server-side AI extraction, but fails to mention potential side effects, error conditions, return values, or prerequisites (e.g., file path accessibility). Adequate but not detailed.

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?

Two concise sentences with front-loaded purpose and key option. No waste; every word adds value.

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?

The description covers the core purpose, file type, and extraction option. It could mention file size limits, format constraints, or return value structure, but given the presence of an output schema (not shown), the omission is acceptable.

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 coverage is 0%, so the description must compensate. It adds meaning for do_not_extract (skip extraction), but file_path is only described by name and as required. No additional semantics for file_path, resulting in partial 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?

The description clearly states the tool uploads large-format drawings (P&ID, plan, elevation, overview) as PDFs to the current project, which distinguishes it from siblings like upload_document and upload_drawing. The verb 'upload' and specific resource types are explicit.

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 provides context for when to use (large-format drawings) and explains the optional do_not_extract parameter. It does not explicitly state when not to use or mention alternatives, but the purpose is clear enough for basic guidance.

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