files.create

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

Lacking annotations, the description carries the full burden but only discloses that a write/upload occurs. Missing: idempotency, file size limits, storage restrictions, return value structure, and whether the optional accountId parameter affects ownership or visibility.

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?

Extremely brief (5 words) and front-loaded with the action. While not verbose, it is inappropriately sized given the lack of schema descriptions and annotations; the brevity constitutes underspecification rather than efficient precision.

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?

Inadequate for a mutation tool handling categorized documents. With no output schema, no annotations, and zero schema descriptions, the description omits critical domain context (e.g., document categories) and operational constraints needed for safe invocation.

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?

With 0% schema coverage, the description fails to compensate. It does not explain filePath (local vs remote?), the enum categories (Evidence, VerificationDocument, Report), or the optional accountId. Only loosely references 'file' which maps to the operation generally.

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?

States a specific verb ('Upload') and resource ('file') with destination ('Ryft'). However, it does not explicitly differentiate from sibling tools like files.get or files.list, though the verb choice implies distinct behavior.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to upload new files vs. retrieving existing ones), nor any prerequisites or conditions for use.

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