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

Lacking annotations, the description must carry the burden. It clarifies the specific attributes returned (number, start and end dates, progress) which provides necessary context about the data the tool delivers, even if not explicitly stated in the schema.

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 definition is highly concise, packing all essential information—the resource, the scope, the parameter definition, and the default setting—into a single, efficient sentence.

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 simplicity of the schema (one optional string parameter) and the lack of annotations, the description is perfectly complete. It allows an agent to understand exactly what the tool returns and how to use the single input parameter.

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?

While the schema defines 'team' as a string, the description provides vital semantic context by explaining the format of the key ('like ONC2') and the default behavior of the parameter when it is not provided ('default: all teams').

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 identifies the resource ('Linear cycles (sprints)') and specifies the precise scope of the operation: retrieving the 'previous, current and next one per team.' This is highly distinct from other listing or querying tools.

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?

It provides guidance on how to use the 'team' parameter, specifically noting that omitting it will default to retrieving cycles for 'all teams.' This helps the agent decide whether to include the parameter based on the user's intent.

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