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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only a boilerplate note about MCP approval requirements and workflow approvals, which does not explain anything about this read operation's behavior, and reads as irrelevant noise.

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?

It is short and front-loaded with the core verb, but the second sentence about approval configuration is unrelated to the tool and does not earn its place. Brevity here reflects under-specification rather than efficient editing.

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?

An output schema exists, so return values need not be described. However, for a five-parameter paginated list tool with zero schema descriptions, the description should at minimum explain the required RFI scope and paging, and it omits all of it.

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 0% across five parameters: rfiId, id, limit, offset, and search are all undocumented. The description does not compensate at all — it never mentions the required rfiId, the default page size of 50 with a 100 cap, offset paging, or that search filters comments.

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?

"Read rfi comments" names a verb and resource, but it nearly restates the tool title and does nothing to separate it from siblings like get_rfi, list_rfis, or create_rfi_comment. An agent knows the general domain but not the distinct role of this tool.

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?

No when-to-use guidance, no prerequisite statement (e.g., an RFI id must already exist), and no named alternative such as get_rfi when a single comment or the parent RFI is needed. The second sentence discusses approval configuration, which is unrelated to listing comments.

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