ntd_days_to_mda

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

No annotations are provided, so the description carries full responsibility for behavioral transparency. It does not disclose whether this is a read-only or mutable operation, any authentication requirements, or what happens if no results match the filter. The description adds minimal behavioral context beyond the schema.

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 short at two sentences, with the key action front-loaded. Every sentence adds value. It could be slightly more concise by omitting 'Optionally' since the schema already indicates optionality.

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 absence of an output schema and annotations, the description should provide more context about return values (e.g., what fields are in each PO, the sort order) and any side effects. It is adequate for a simple filter tool but lacks details that would help an agent predict behavior.

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 20% (1 out of 5 parameters has a description: max_days). The description adds the concept of 'days until planned MDA' as the sort criterion, which is not in the schema. However, four parameters (drug, year, donor, country) have no descriptions in either the schema or the tool description, leaving a gap.

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 uses a specific verb ('Find') and resource ('POs sorted by days until planned MDA'), and distinguishes itself from siblings like ntd_list_pos, which likely returns all POs without this sorting. However, it could be clearer that the output is sorted in ascending order.

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 states 'Optionally filter and/or limit by a maximum day threshold', which gives some context on when to use filtering but does not explicitly distinguish this from siblings like ntd_list_pos or ntd_summary_stats, nor does it mention when not to use this tool.

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