accelo_get_milestone

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

No annotations are provided, so the description must carry the behavioral burden. 'Get' implies a read-only operation, but the description does not disclose auth requirements, error behavior for missing IDs, rate limits, or any other behavioral trait beyond the basic retrieval.

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 two short lines plus a compact Args block. The core purpose is front-loaded, and every sentence and parameter note serves a clear purpose with no wasted text.

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 simple single-resource retrieval tool, the description covers purpose and parameter meaning adequately. However, with no output schema and no annotations, it leaves return shape, error handling, and permissions unaddressed, so it is only minimally 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 description coverage is 0%, so the description is the only documentation for parameters. It identifies 'id' as a Milestone ID and 'fields' as additional fields to return, adding some meaning over bare schema titles, but it omits format details such as whether fields is a comma-separated list.

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 states a specific verb and resource: 'Get a single milestone by ID.' The word 'single' distinguishes it from list/count milestone tools, though it does not name the sibling directly. The purpose is clear without needing to inspect the schema.

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?

Usage is implied by 'by ID': the tool is for retrieving one milestone when its identifier is known. However, there is no explicit guidance on when to use this rather than accelo_list_milestones or accelo_count_milestones, and no when-not conditions are stated.

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