oncofiles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that results are 'persisted in the structured_metadata column', indicating a write operation, but lacks details on permissions required, whether the operation is idempotent, error handling, or performance characteristics. For a tool that modifies data, this is insufficient transparency.

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, starting with a clear purpose statement followed by details. The 'Args' section is structured but slightly verbose; every sentence adds value, though it could be more streamlined without losing clarity.

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 the tool's complexity (AI analysis, metadata extraction, persistence) and the presence of an output schema (which covers return values), the description is reasonably complete. It explains the process and parameter semantics well, though it lacks behavioral context like error cases or side effects, which is a minor gap.

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 description includes an 'Args' section that explains the single parameter ('document_id: The local document ID to extract metadata from'), adding meaning beyond the input schema's basic type definition. Since schema description coverage is 0%, this compensates well, though it doesn't specify format constraints or 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 clearly states the tool's purpose with a specific verb ('extract and store') and resource ('structured medical metadata from a document'), distinguishing it from siblings like 'extract_all_metadata' by focusing on medical metadata and persistence. It explicitly mentions the AI analysis and specific metadata types (findings, diagnoses, medications, providers, patient-friendly summary), providing comprehensive detail.

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 provides no guidance on when to use this tool versus alternatives like 'extract_all_metadata' or 'enhance_documents', nor does it mention prerequisites or exclusions. It only states what the tool does without contextual usage instructions, leaving the agent to infer when it's appropriate.

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