list_service_maintenances

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions that the list includes both 'scheduled and past' windows, but does not address ordering, pagination, relevance filtering, or any error conditions. The description is too brief to fully inform an AI agent of the tool's behavior.

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 sentence that efficiently conveys the core purpose. It is front-loaded with the action and resource. While it could be slightly more structured (e.g., including parameter clarification), it avoids unnecessary words and earns its place.

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 tool's simplicity (one parameter, has output schema) and the existence of sibling tools, the description provides minimal context. It does not explain how this tool differs from 'list_maintenance_windows', nor does it mention expected output structure (though output schema covers that). The description is adequate but leaves room for improvement.

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 input schema has one required parameter 'slug' (string), but the description does not explain what 'slug' represents. With 0% schema description coverage, the description adds no semantic meaning beyond the schema. The agent must infer that 'slug' identifies the catalog service.

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 'List scheduled and past maintenance windows announced by a catalog service', which specifies the verb (list) and resource (maintenance windows for a specific service). The example 'e.g. upcoming AWS maintenance that could affect you' adds concrete context and helps differentiate from siblings like 'list_maintenance_windows' that likely list all windows.

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 implies the tool is for listing maintenance windows of a specific catalog service, but it does not explicitly state when to use it versus alternatives like 'list_maintenance_windows' or 'get_maintenance_window'. No guidance on prerequisites or when not to use it is provided.

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