ntd_list_pos

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

No annotations are provided, so the description bears the full burden. It explains that results include milestone progress and mentions valid filter values, but does not disclose mutation safety, required permissions, pagination behavior, or what happens when no filters are applied (e.g., returns all POS). Adequate but not thorough.

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 remarkably concise—only three sentences. The first sentence states the core function and output. The second lists donors and drugs. The third lists regions. Every sentence adds value without redundancy.

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 has no output schema and the parameter count is moderate (7, all optional), the description adequately covers the tool's purpose and the key filter values. It does not explain default behavior when no filters are applied, or return format details, but for a list tool, this is fairly complete.

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 coverage is 100%, so each parameter already has a description. The tool's description adds context about the purpose (returns milestones) but does not elaborate on parameter behavior beyond what the schema already provides, such as how multiple filters interact or the format of country partial matches.

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 lists POs with optional filters, returns key fields and milestone progress per PO. This distinguishes it from siblings like ntd_get_po (single PO retrieval) or ntd_get_milestones (milestones only).

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 lists acceptable values for donors, drugs, and regions, which helps users construct valid filters. However, it does not explicitly tell when to use this tool vs. alternatives like ntd_summary_stats or ntd_days_to_mda, nor does it mention prerequisites or when not to use it.

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