microcms_get_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states 'get a list' without mentioning pagination behavior, filtering capabilities, or response characteristics. The 11 parameters are described in the schema but the description adds no additional context about trade-offs or limitations.

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 of 6 words, which is concise but too brief for a tool with 11 parameters and no annotations. It front-loads the purpose but omits critical details, resulting in under-specification rather than effective conciseness.

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 complex tool with 11 parameters and no output schema, the description is incomplete. It does not explain pagination, filtering, or how results are returned. Sibling tools exist but are not differentiated. Given the lack of annotations, the description should provide more contextual information.

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 100%, so all parameters are already documented with descriptions. The tool description adds no extra meaning beyond the schema, which provides details like min, max, and examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Get a list of contents from microCMS', specifying the verb 'Get' and the resource 'list of contents from microCMS'. This effectively distinguishes it from sibling tools like microcms_get_content (single item) and microcms_get_list_meta (metadata only).

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?

No guidance is provided on when to use this tool versus alternatives such as microcms_get_content for a single item or microcms_get_list_meta for metadata. The description does not mention context, prerequisites, or exclusions.

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