botdigit_list_contract_milestones

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

No annotations are provided, so the description carries the burden alone. The verb "List" signals a non-mutating read and the phrase "escrow funding" discloses an extra data dimension beyond the title, but nothing is said about permissions, pagination, ordering, or empty-result behavior.

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?

A single short sentence with the action verb and scope front-loaded and no filler. It is efficient, though the extreme brevity leaves no room for the qualifying details an agent would otherwise benefit from.

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 one-parameter, read-only list tool with no output schema this is minimally adequate: purpose and scope are clear. It stops short of being complete because return content, ordering, and pagination are beyond a no-annotation description's scope here.

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 100% for the single contract_id parameter, so the schema already documents the UUID requirement. The description only restates the scoping ("a specific contract") and adds no format or constraint detail beyond it, matching the baseline 3.

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?

States a specific verb (List) and resource (milestones and escrow funding) scoped to a specific contract, so the agent knows exactly what it returns. It does not explicitly contrast itself with related siblings such as botdigit_get_contract or botdigit_list_contracts, which keeps it short of a 5.

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?

"For a specific contract" implies the tool is used once a contract is already known and that an identifier is required, but it never states when to prefer this over get_contract or how it relates to the contract-level listing. Usage is only implied, not spelled out.

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