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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the response shape (author, text, time) and the underlying endpoint, which is useful, but it says nothing about pagination, ordering defaults, or permissions.

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 short sentences, zero filler, with the resource and returned fields front-loaded before the endpoint reference.

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?

With no output schema, the description helpfully discloses the returned fields, and the schema fully covers the six query parameters. Only minor gaps remain: no pagination/next_offset guidance in prose and no note on default ordering for a list endpoint.

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% and all six parameters are documented in the schema (sort, limit, fields, offset, direction, opportunity_id), so the schema carries the heavy lifting. The description adds no parameter-level meaning beyond noting the target is an opportunity.

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 names the specific resource (comments on an opportunity) and enumerates the returned content (author, text, time), so it is clearly distinguishable from the write-side sibling getfly_add_opportunity_comment. The verb 'list' only comes from the name, not the prose, so it stops short of a full 5.

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?

Usage is only implied by the resource naming and the 'discussion' framing; there is no explicit statement of when to call this versus getfly_get_opportunity or getfly_add_opportunity_comment. No prerequisites or exclusions are given.

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