list_guides

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

No annotations are present, so the description must fully disclose behavior. It states the scope ('all guides') but does not mention the return format, pagination, ordering, or filtering behavior beyond the schema's optional category field. This is minimal transparency for a listing 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?

The description is a single, front-loaded sentence that directly states the tool's purpose and enumerates the covered topics. Every word earns its place; there is no 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 low-complexity list tool with one optional enum parameter, the description adequately conveys scope and category coverage. However, since there is no output schema, a brief note about the return structure or how this relates to get_guide for detailed viewing would improve completeness.

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 for the single optional 'category' parameter is 100%, including an enum and a description. The tool description lists categories in prose, but this largely duplicates the schema and adds no meaningful semantic detail beyond what is already structured.

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 the action ('list') and resource ('all MAX documentation guides'), and enumerates specific categories (platform, bot creation, SDK, mini-apps, channels, partners, legal). This distinguishes it from sibling tools like get_guide (retrieving a single guide) and list_endpoints.

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 a generic listing use case but does not explicitly state when to use this tool versus get_guide, search_docs, or list_endpoints. No exclusions or alternative recommendations are provided; the category filter is only present in the schema, not described in the tool description.

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