cbd_guide

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

With no annotations, the description carries the full burden. 'Guides' implies a safe, read-only operation retrieving informational content. While it doesn't detail potential behavior like pagination or external dependencies, the nature as a guide is sufficiently clear.

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 concise sentence that front-loads the purpose and lists all topics. It is efficiently brief, though using English could improve clarity for non-French agents.

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?

No output schema is provided, and the description does not explain what the guide returns (e.g., plain text, markdown) or how to interpret the result. This leaves the agent unsure about the response format.

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% (enum values listed with descriptions). The tool description merely restates the topics without adding new meaning or context beyond the schema.

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 it provides complete CBD guides, listing 12 specific topics. The verb 'Guides' combined with the topic list makes the purpose explicit and differentiates from sibling tools like cbd_market_data or cbd_news.

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 use for getting guides on CBD topics, but lacks explicit when-to-use or when-not-to-use guidance. Sibling tools (e.g., search_cbd_products) suggest alternatives, but no direct exclusions or context are provided.

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