simulate_concentration_time

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

The 'Agent contract' provides some behavioral context (e.g., preserving fields, not inferring facts) beyond what is in the schema or annotations, but it does not disclose common traits like mutation, side effects, or performance implications.

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 brief with two sentences, but the second sentence is lengthy and mixes output-handling instructions with the purpose, slightly reducing 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?

The description lacks details on parameter units, acceptable ranges, or differentiation from similar tools. Given the presence of an output schema, return values are partially covered, but overall the description is insufficient for an agent to use the tool reliably.

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 only 33%, and the description adds no information about the required parameters (dose, vd, ke, time). The agent must rely solely on parameter names, which may be ambiguous without units or context.

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 function: 'Run a one-compartment concentration-time estimate.' This is a specific verb+resource combination that distinguishes it from siblings like simulate_pk_interaction and other dosing calculation tools.

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?

No guidance on when to use this tool versus alternatives. The 'Agent contract' advises on handling output but does not specify use cases or when not to use the tool.

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