assets_sign

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

Discloses default TTL (1 hour) and maximum (7 days), and that it generates a presigned URL without exposing credentials. No annotations are provided, so the description carries the burden. It reasonably covers the key behavior, though does not mention potential side effects like logging or whether the blob must 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?

Two sentences, 26 words. Front-loaded with action and purpose. No unnecessary words—every sentence 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?

Complete for the tool's simplicity. Lacks mention of return value (presigned URL) and any prerequisites (blob must exist), but the overall purpose is well-covered. No output schema exists, so description could hint at what is returned, but the need is less urgent.

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 has 100% coverage with descriptions for all three parameters. The description adds value by stating default TTL (1 hour) and max TTL (7 days), which complements the schema-defined min/max. Does not elaborate on project_id or key beyond schema, but those are self-explanatory.

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?

Description clearly states it generates a time-boxed S3 presigned GET URL for a blob, and distinguishes the purpose (sharing externally without exposing apikey). This effectively differentiates it from sibling tools like assets_get or assets_put.

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?

Explicitly says 'Use this to share a private blob externally without exposing your apikey', indicating the primary use case. Does not mention when not to use or alternatives, but the context is clear given the siblings.

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