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 domain-specific transparency by stating that no quote, booking, payment, message, or provider request is created, which gives assurance beyond the generic annotation hints.

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?

Two short sentences with no filler. The core operation is front-loaded, and the side-effect guarantee is provided in a compact second sentence. Every word earns its place.

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 two-parameter read operation, the description covers the purpose, required identifiers, and side-effect profile. An output schema exists, so return-value documentation is not the description's burden. It is slightly incomplete only in not explaining how to obtain a resumeToken or how this relates to prepare_offer.

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 0%, so the description needed to explain what submissionId and resumeToken mean, where they come from, and how they relate to a prepared offer. It only repeats the parameter names in the operation statement, adding almost no semantic value beyond what the parameter names and schema formats already imply.

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 and resource: 'Read one prepared offer' by its two identifying tokens. It clearly separates this read operation from quote, booking, payment, message, and provider request creation, which distinguishes it from siblings like quote_ride and prepare_offer.

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 gives clear context that this is a read-only lookup of a prepared offer, and the explicit statement that no quote or booking is created indirectly signals when not to use it. However, it does not name alternatives or give explicit when-to-use versus when-not-to-use guidance beyond that side-effect disclaimer.

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