Fetch CometChat Documentation Page

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

The annotations already declare readOnlyHint=true, confirming the tool is safe. The description adds value by stating the return format (markdown) and metadata (title, section), which is beneficial beyond the annotation. No side effects or rate limits are mentioned, but for a simple read tool 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 consists of two well-structured sentences with no extraneous information. The first sentence states the core function and output, the second clarifies input format. Every word 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 low complexity (1 parameter, simple read operation, annotations present, no output schema), the description is fully adequate. It covers the tool's purpose, input options, and output type, leaving no obvious gaps for an AI agent to misunderstand.

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 is 100% for the single parameter 'path'. The description adds further clarity with concrete examples (full URL and relative path), which enhances understanding beyond the schema's description. This justifies a score above the baseline of 3.

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 tool fetches the full content of a single CometChat documentation page, distinguishing it from sibling tools like search (which returns snippets) and implementation bundle (different resource). The verb 'fetches' paired with 'documentation page' is specific and unambiguous.

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 explains the input format (URL or path) with examples, but does not provide explicit guidance on when to use this tool versus its siblings (e.g., 'Use this when you need the full page content'). The usage is implied by the purpose, but no alternatives or exclusions are mentioned.

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