get_list_comments

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

Discloses ordering ('newest first') and return fields (id, text, author, date). No annotations present, so description carries full burden. Could mention pagination or limits for completeness, but adequate for simple read.

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?

Two concise sentences with key information front-loaded. No wasted 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?

For a simple tool with one parameter and no output schema, description covers purpose, behavior, return data, and differentiation. Sufficient for agent to use correctly.

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 provides description for list_id. Tool description adds context about list-level discussion but not beyond schema. Baseline 3 due to 100% schema coverage; description does not significantly enhance parameter understanding.

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?

Description states specific verb 'List', resource 'comments', and scope 'attached to a List', clearly distinguishing from individual task comments. No ambiguity.

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?

Explicitly distinguishes from get_task_comments by noting 'List-level discussion, separate from individual task comments', guiding selection. Does not mention when not to use (e.g., for writing comments) but provides clear context.

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