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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing the return content (schema definition as inline schemaJson or linked schemaId, rowVersion, optional usage). It does not contradict annotations. While it omits error behavior, for a read-only getter this is adequate beyond the annotation baseline.

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 two sentences, front-loaded with the core purpose and key return fields. It ends with a necessary prerequisite (project context). No wasted words; every clause contributes to understanding the tool.

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?

Given no output schema, the description explains the primary return elements (schema definition, rowVersion, optional usage). It also states the context requirement. It does not cover edge cases like not-found behavior, but for a simple get with two required parameters and read-only annotation, the coverage is sufficient. A 4 is warranted because the description is informative without being exhaustive.

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%, so the schema already fully documents specId, requestBodyComponentId, and includeUsage. The description mentions includeUsage's effect ('usage details showing which endpoints link it') but adds no new meaning beyond the schema. Baseline 3 is correct because the description does not compensate for any coverage gap.

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 request body component, specifying its contents (schema definition, rowVersion) and optional usage details. It is distinct from siblings like list_request_body_components (which lists) and get_response_component (which targets a different resource type). The verb 'Get' and specific resource make purpose unambiguous.

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?

The description notes 'Requires project context', which is a clear prerequisite for using the tool. It does not explicitly mention when to prefer this over alternatives (e.g., list_request_body_components for enumeration), but the scope is clear. This qualifies as clear context without exclusions, so a 4 is appropriate.

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