oncofiles

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

With no annotations provided, the description carries full burden. It discloses that the tool stores documents persistently and auto-parses legacy filename formats, which are useful behavioral traits. However, it doesn't mention authentication requirements, rate limits, error conditions, or what happens on successful upload (though output schema exists).

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 appropriately sized and front-loaded with the core purpose. The filename convention details are necessary but could be more efficiently structured. The 'Args:' section clearly separates parameter semantics from the introductory text, though some redundancy exists in filename explanations.

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?

Given 3 parameters with 0% schema coverage and an output schema present, the description provides strong parameter semantics and clear purpose. It covers filename conventions thoroughly. The main gap is lack of behavioral context about permissions, errors, or integration with sibling tools, but the output schema reduces the need to explain return values.

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 0%, so the description must compensate fully. It provides detailed semantic information for all 3 parameters: content requires Base64 encoding, filename follows specific naming conventions with examples, and mime_type has a default value mentioned. This adds substantial value beyond the bare schema.

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 specific action ('Upload a medical document') and target resource ('to persistent storage'), distinguishing it from sibling tools like 'delete_document', 'get_document', or 'view_document'. The verb 'upload' is precise and differentiates it from related operations.

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 implies usage context through filename conventions and legacy format acceptance, but doesn't explicitly state when to use this tool versus alternatives like 'sync_to_gdrive' or 'enhance_documents'. No explicit guidance on prerequisites, timing, or tool selection criteria is provided.

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