upload_document

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

No annotations provided; description only states uploading a PDF and returning a document id. Does not disclose file size limits, supported formats beyond PDF, error handling, authentication requirements, or whether action is reversible. With zero annotation coverage, the description fails to adequately convey behavioral traits.

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 sentences, no unnecessary words. Front-loaded with action and result. Efficient and scannable.

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?

Tool has one parameter, no output schema, no annotations. Description covers purpose and return value but lacks details on error scenarios, file limits, or integration with other tools. Adequate for a simple upload but could be more complete.

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% (filePath described as 'Absolute path to a PDF file'). Description adds minimal value beyond schema ('from a local file path'). Baseline score of 3 is appropriate as schema already documents parameter clearly.

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?

Clearly states verb 'upload' and resource 'PDF from a local file path'. Specifies return value (document id) and its role in creating envelopes. Distinguishes easily from sibling tools that analyze documents, create/send envelopes, etc.

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 explicit guidance on when to use this tool vs alternatives (e.g., analyze_document, create_envelope). Missing prerequisites, recommended order of operations, or conditions to avoid. Only a basic description of functionality.

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