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

Annotations already declare readOnly, idempotent and non-destructive, so a read tool's safety profile is covered. The description adds real behavioral detail beyond them: only the 20 newest comments are returned, include_history appends the change log, and the git branch name is included. It stops short of noting pagination or truncation for the comment set, but the limits it does state are valuable.

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?

One dense sentence, front-loaded with the core action ('One item in full'), followed by a colon-delimited inventory that stays scannable. Every element listed is a distinct returned field, though the length is near the limit for a single sentence.

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 read-only annotations and an output schema already present, the description does not need to explain return values, yet its field inventory plus the comment-count and history limits make the tool's behavior unambiguous. No gaps that would cause a mis-invocation, only the absence of sibling routing guidance.

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 coverage is 100%, so the baseline is 3, and the description earns above that by giving the purpose of each parameter: comment ids are surfaced specifically 'for edit_comment', and include_history is framed as adding the change log. That cross-tool linkage is meaning the schema alone does not supply.

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?

States a specific retrieval verb and resource ('one item in full') and enumerates exactly what comes back, so the agent knows this is the single-item deep fetch. It does not name a sibling like search_items, so the single-vs-list distinction is implied rather than explicit.

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 implied: fetch one item by key when you need its full detail. There is no statement of when to prefer this over search_items, run_view, or my_work, and no note on prerequisites such as knowing the key. Minimum viable context only.

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