list_months

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

No annotations are provided, so the description carries the full burden. It discloses the default behavior of exclude_fields (model's default list, with options to return all or override). This adds valuable behavioral context beyond the schema. For a read-only list operation, this is sufficient.

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 one short sentence followed by clear parameter descriptions with formatting. Every sentence adds value, no fluff, and the structure is easy to scan.

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 presence of an output schema, the description does not need to detail return values. It covers purpose, parameter usage, and the special behavior of exclude_fields. Missing details like pagination or ordering are not critical for a list tool of months, so it is adequately complete.

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 description coverage is 0%, so the description must compensate. It fully explains both parameters: plan_id references list_plans; exclude_fields details three behaviors (default, empty array for all, custom override). This adds significant meaning beyond the schema's type and default null.

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 explicitly states 'List all plan months', clearly identifying the verb (list) and resource (plan months). The sibling tools include 'get_month' (singular), so this tool is distinct in listing multiple months.

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 provides guidance for the plan_id parameter by referencing list_plans to find available IDs. It also explains the exclude_fields behavior (default, get all, custom list). However, it does not explicitly state when to use this tool versus other listing tools or give when-not-to-use guidance.

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