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 covered. The description adds useful behavioral context by emphasizing 'every membership-tier pricing configuration,' indicating the tool returns all pricing tiers for the service rather than a single one.

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 a single, tightly written sentence that leads with the key verb 'Read' and contains no filler or redundant phrases. Every word contributes to identifying the tool's action, resource, and scope.

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 read tool with one required parameter, complete schema coverage, an output schema, and annotations covering idempotence and non-destructiveness, the description is fully adequate. It tells the agent what is read and for which entity, and nothing essential is missing.

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% for the single serviceId parameter, and the schema already describes it as a 'Booking service ID' with a uuid format. The description simply restates the scope ('one booking service') without adding new parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Read') with a precise resource ('membership-tier pricing configuration') and scope ('for one booking service'). This clearly distinguishes it from sibling tools like set_service_tier_pricing and copy_service_tier_pricing without needing to open the schema.

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 verb 'Read' implies this tool is for retrieval rather than modification, but the description does not explicitly state when to prefer it over alternatives or mention that set_service_tier_pricing/copy_service_tier_pricing exist for write/copy operations. The usage context is implied, not stated.

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