add_biometric

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Add a biometric entry' without any details about idempotency, duplicate handling, side effects, or required permissions. This leaves significant gaps for an AI agent.

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 concise: a brief opening sentence followed by structured lists. The most important information is front-loaded. It could be slightly more streamlined, but it is well-organized and avoids unnecessary details.

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?

For a simple add operation with three required parameters, the description fully covers the input. The presence of an output schema (though not visible) reduces the need to explain return values. The description is sufficiently complete for an agent to use the tool correctly.

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 allowed values for metric_type, units for value, and format for entry_date. The input schema only has titles and types with 0% coverage, so the description adds crucial meaning beyond the 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 'Add a biometric entry to Cronometer' and lists supported metric types. The tool name and description align, and it is distinguished from sibling tools like 'remove_biometric' and 'get_recent_biometrics'.

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 specifies supported metric types and displays acceptable units (lbs, mg/dL, bpm, %), guiding appropriate usage. It implicitly tells the agent when to use this tool (for adding these specific metrics) but does not explicitly state conditions to avoid or alternative tools.

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