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

Beyond the sparse annotations, the description exposes key behaviors: the signed URL is short-lived, the file_id expires after 24 hours, uploads are limited to 25 MB, and only a MIME whitelist is allowed. It also clarifies the upload mechanism and that binary data never enters the agent context, which is valuable behavioral context.

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 compact and front-loaded: purpose first, then the upload workflow with a concrete curl example, then limits and expiry. Every sentence contributes actionable information with no filler.

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 tool with no output schema and minimal annotations, the description supplies all essentials: what is returned (signed_url and file_id), how to use them, size limits, MIME restrictions, expiration, and the required follow-up call. An agent has enough to invoke it correctly.

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 input schema already covers all three parameters at 100%, so the baseline is 3. The description adds meaningful semantics by explaining how content_type is used in the PUT request and by listing the allowed MIME types, going beyond the schema's basic examples.

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 and resource: 'Issue a short-lived signed URL to upload an Excel/CSV file straight into Storage.' It also clearly differentiates this from layerz_parse_file by framing parse_file as the downstream step, so an agent knows the tool's exact role.

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 gives explicit context on when to use this tool: when a file must be uploaded to Storage without entering the agent context, followed by layerz_parse_file. It does not explicitly enumerate when-not-to-use cases or alternatives, but the workflow is unmistakable.

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