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

The readOnlyHint annotation already indicates a read-only operation. The description adds behavioral detail by mentioning the optional includeUsageCounts parameter, which affects the response content. It does not contradict the annotation, and no side effects are described. The description goes slightly beyond the annotation by highlighting the feature that alters behavior.

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 only two sentences. It front-loads the primary purpose and then adds the optional feature and requirement. No unnecessary words or repetition, ensuring efficient parsing by an agent.

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 there is no output schema, the description does not need to explain return values. It adequately covers the tool's purpose, the optional feature, and the context requirement. For a simple list operation, this is complete information for an agent to decide when and how to invoke 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?

The schema provides full descriptions for all three parameters, covering 100% of the input schema. The description does not add significant new meaning beyond the schema, as the usage counts feature is already described in the includeUsageCounts parameter. Baseline 3 is appropriate given the complete schema coverage.

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's function: listing reusable request body components (OpenAPI components/requestBodies). It also mentions the optional usage counts feature, which distinguishes it from sibling tools that list other component types. The verb 'List' is specific and the resource is 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 implicitly instructs the agent to have context set. It does not explicitly state when to prefer this over sibling list tools (e.g., list_header_components), but the component type in the title and description makes the selection clear. This is adequate guidance, though a direct comparison would improve it.

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