list_releases

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

Discloses default page size, max limit, nesting depth (3 levels), and case normalization for type. Lacks explicit read-only assertion, but browsing intent is clear. No annotations to contradict.

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?

Two sentences, first covers purpose, second covers key filters and behaviors. No wasted words, information is front-loaded.

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?

Covers essential behaviors (pagination, nesting, filters) with 10 parameters and no output schema. Could mention sorting options, but schema enum suffices. Reasonably complete for a list tool.

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?

Description adds value beyond schema by explaining default page size for limit, nesting behavior for parentReleaseId, and case normalization for type. Schema coverage 60% is reasonable, and description compensates well.

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?

Clearly states 'Browse releases (a.k.a. milestones) for a project' with specific verb and resource. Distinguishes well from sibling tools like get_release (single) and create_release (creation).

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?

Provides explicit guidance on when to use each filter (search, type, isCompleted, parentReleaseId). Does not explicitly mention alternatives like get_release for a single release, but the context is clear enough.

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