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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that retrieval is by single ID, and says nothing about error behavior for missing/unknown IDs, which would be the useful addition for a fetch tool.

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?

A single short sentence with no filler; the essential information (verb, resource, identifier-based lookup) is front-loaded and nothing is wasted.

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 single-record read with full annotation coverage and complete schema documentation, the description is sufficient to call the tool correctly. It is slightly thin on return-shape expectations, but no output schema is expected to exist here.

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 there is exactly one required parameter ('id', described as the infrastructure asset comment ID), so the schema fully documents it. Baseline 3 applies; the description adds no format or syntax detail beyond the schema.

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 states a specific verb ('Get'), resource ('infrastructure asset comment'), and retrieval scope ('a single ... by ID'). It is clear what the tool does, though it does not explicitly distinguish itself from the sibling list_infrastructure_asset_comments or get_asset_comment.

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?

There is no guidance on when to use this tool versus alternatives like list_infrastructure_asset_comments or the singular-by-ID vs lookup patterns. The 'by ID' phrasing implies a single-record fetch, but no context or prerequisites are given.

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