List Shortcut Milestones

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'list' without explaining return format, sorting, limits, or the purpose of the dry_run parameter. It does not contradict annotations (none exist), but it is very thin.

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 concise sentence, which is easy to parse, but it is so short that it borders on underspecification. It earns no extra credit for being front-loaded because it contains so little information.

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 list tool, the description leaves critical gaps: no mention of output format, no explanation of dry_run, and no usage guidance. Since there is no output schema, the description should at least hint at what a milestone entry looks like, but it does not.

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?

The only parameter, dry_run, is a boolean with no description in the schema. The tool description does not mention it at all, leaving the agent without any clue what dry_run does. With 0% schema coverage, the description fails to compensate.

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 verb and resource: "List milestones in your Shortcut workspace." It unambiguously identifies this as a list operation for milestones, distinguishing it from sibling list tools like list_epics or list_projects.

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 gives no guidance on when to use this tool versus alternatives (e.g., get_milestone, list_milestone_epics), nor does it mention any filtering, pagination, or prerequisite context. It is bare of usage direction.

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