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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description goes beyond that by disclosing the shape of the response (inclusions, price, onboarding, page URL), which is valuable given there is no output schema. It does not cover failure behavior for an unknown id, so not a 5.

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?

A single sentence with the identity and provenance of the input front-loaded followed by the returned contents. Every clause carries information; nothing is padding.

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 one-parameter read-only getter with no output schema, the description plus annotations cover everything needed: what identifies the record, where the id comes from, and what fields come back. Nothing an agent needs to call it correctly 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 description coverage is 100% and the id parameter already documents its origin ('Service id from list_services, e.g. care-plan'), so the description's 'by id (from list_services)' adds no meaning beyond the schema. Baseline 3 is correct when the schema carries the parameter semantics.

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?

States a specific verb and singular resource ('Returns one Solidmade offer by id') and immediately distinguishes itself from the sibling list_services by noting it takes an id that came from that listing. The added clause enumerates the payload (inclusions, price, how to start, page URL), so an agent knows exactly what it gets.

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 parenthetical '(from list_services)' makes the retrieval order explicit: call list_services first to obtain an id, then call this tool. There is no guidance on when not to use it or when request_quote is the better sibling, which keeps it short of a 5.

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