ntd_get_po

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

No annotations are provided, so the description carries the full burden. It states the tool fetches details and milestones, but does not disclose whether this is a read-only operation, any required permissions, or side effects. Minimal behavioral context beyond the basic action.

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 a single, clear, front-loaded sentence with no unnecessary words. It efficiently communicates the tool's purpose and key parameters.

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 is moderately simple (1 param, no output schema), the description suffices for basic use. However, missing details like what 'full details' includes, how milestone dates are formatted, or whether the PO number must be a specific format could leave gaps for an AI agent.

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 0%, so the description must compensate. It mentions the single parameter po_number by name and implies it is a PO identifier, but does not specify format, required length, or any constraints. The description provides basic context but lacks detail to fully replace 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 retrieves full details and milestone dates for a single PO by PO number. It distinguishes itself from siblings like ntd_list_pos (which presumably lists POs) and ntd_get_milestones (which may focus just on milestones).

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 implies use when you need comprehensive PO details for one PO, but does not explicitly say when to avoid it (e.g., if only milestones are needed, use ntd_get_milestones; if summary stats, use ntd_summary_stats). No alternatives or exclusions are mentioned.

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