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

The readOnlyHint annotation already indicates a non-destructive operation, and the description adds useful behavioral details such as requiring project context and the effect of setting includeUsage. No contradictions or hidden side effects are mentioned.

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 concise, consisting of three focused sentences with no redundant or irrelevant information. It front-loads the core purpose and then provides necessary usage context.

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 GET-like tool with no output schema, the description sufficiently explains what will be returned (schema, headers, rowVersion) and the optional includeUsage behavior. It also communicates the project context prerequisite, making it complete enough for an agent to call correctly.

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?

The schema already covers all three parameters with meaningful descriptions. The tool description adds some usage nuance, such as having the component ID beforehand, but does not significantly expand parameter semantics beyond what the schema provides.

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 states the tool retrieves a single reusable response component with its schema, headers, and rowVersion. It also distinguishes itself from list_response_components by specifying that it is for when a component ID is already known.

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 tells the user to use this tool when they already have the component ID and directs them to list_response_components for browsing or finding an ID. It also notes that project context is required, giving clear when-to-use guidance.

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