List seasons of a ground

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

With no annotations provided, the description carries full behavioral burden. It discloses the human-only creation constraint, chronological ordering, and the summary vs full view behavior including the specific fields returned. It doesn't cover errors or auth, but these are not critical for a read-only list operation.

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?

Three sentences, each earns its place: first states the core function, second gives an essential constraint/rule, third explains the parameter effect and output. Front-loaded and free of fluff.

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 2-parameter tool with no output schema, the description explains the return format (summary fields vs full metadata) and points to an external rule for the human-only constraint. It lacks pagination details, but the tool is simple and likely not paginated. Overall sufficient.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the default view ('summary') and what 'view=full' includes ('metadata'), plus listing the exact fields in the default summary. This goes beyond the schema's brief descriptions.

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+resource ('Returns the seasons of a ground') and adds distinct scope ('in chronological order'), clearly differentiating it from sibling list tools like list_bugs and list_events. The purpose is immediately obvious.

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 that seasons are human-only and creation via MCP is prohibited, with a reference link. This acts as a 'when not to use' instruction. It doesn't explicitly contrast with sibling list tools, but the exclusion and default view explanation offer clear context.

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