find-comments

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is covered. The description adds the critical exclusive-or constraint among the three identifiers, which is not visible in the schema (since all params are optional). This provides valuable contextual behavior beyond the annotations.

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 two sentences: the first states the purpose and modes, the second states the mandatory constraint. No filler or redundancy.

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 retrieve tool with a rich schema and output schema, the description adequately conveys the main purpose and key constraint. It doesn't explain pagination details, but those are covered by the schema's limit/cursor descriptions. Slight lack of explicit guidance on pagination usage, but overall sufficient.

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 has 100% coverage for all parameter descriptions, so the baseline is 3. The description adds the exclusive-or rule and clarifies the three usage modes (task, project, comment ID), giving semantic meaning beyond the individual field descriptions.

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 identifies the tool as a retrieval operation ('Find comments') and specifies the three available lookup modes (by task, project, or ID). This distinguishes it from sibling tools like add-comments and update-comments.

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?

It explicitly states the parameter constraint ('Exactly one of taskId, projectId, or commentId must be provided'), which guides when to use each mode. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a 5.

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