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 clearly indicates this is a write operation ('Save'), but doesn't mention permissions, whether entries are editable/deletable, or any rate limits. The description adds useful context about the oncology journey domain, but lacks important behavioral details for a mutation tool.

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 well-structured with a clear purpose statement followed by usage guidance and detailed parameter explanations. Every sentence adds value, though the parameter section is somewhat lengthy. It's appropriately sized for a tool with 7 parameters and good front-loading of the core purpose.

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 (7 parameters, mutation operation) and the presence of an output schema (which means return values don't need explanation), the description is quite complete. It covers purpose, usage context, and detailed parameter semantics. The main gap is lack of behavioral details like permissions or mutation consequences, but with an output schema, this is less critical.

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 description coverage and 7 parameters, the description provides excellent parameter semantics. It clearly explains each parameter's purpose, format, and defaults where applicable (e.g., 'Defaults to today' for entry_date, 'Comma-separated tags' for tags, 'Type of entry: summary, decision, progress, question, note' for entry_type). This fully compensates for the lack of schema descriptions.

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 ('Save') and resource ('diary entry to the conversation archive'), and distinguishes it from siblings by specifying it's for logging narrative content about the oncology journey. It provides concrete examples of what to log (summaries, decisions, progress notes, questions), making the purpose highly specific and differentiated.

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 clear context for when to use this tool ('to log summaries, decisions, progress notes, questions, or any narrative content from conversations about the oncology journey'), which helps distinguish it from sibling tools like add_activity_log or add_research_entry. However, it doesn't explicitly state when NOT to use it or name specific alternatives, keeping it from a perfect score.

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