List Comments

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

No annotations are provided, so the description carries the full burden for disclosing behavior. It only says 'list comments' without mentioning pagination, ordering, default limits, or how filters combine. For a listing tool, this is minimal and does not disclose return format or potential side effects.

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 is front-loaded and contains no fluff. It effectively communicates the primary function and key filter capability in minimal words.

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?

The tool has no annotations and no output schema, so the description must carry more weight. It fails to mention pagination behavior, default limits, or the shape of the return value. Given the existence of sibling comment tools, more context on when this is appropriate would be expected.

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?

The description mentions 'optional market/event filter' which clarifies the purpose of event_id and market_id parameters. However, it does not explain the limit and offset parameters, which are also present in the schema. With 0% schema description coverage, the description partially compensates but leaves gaps.

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 states a clear verb+resource: 'List comments' with an optional filter by market/event. This distinguishes it from sibling tools like get_comments_by_id and get_comments_by_user, though it does not explicitly name them. It is specific enough to understand the core function.

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 usage for listing comments with filters but provides no explicit guidance on when to choose this tool over alternatives like get_comments_by_id or get_comments_by_user. No exclusions or alternative recommendations are given.

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