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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), it discloses metering economics (a fresh guide consumes Pro allowance, exact-cached guides are unmetered), the underlying pipeline, and idempotency behavior (identical request_key results are persisted, so retries never start a second provider request). This is rich operational context an agent could not derive from the structured fields.

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 core action and its prerequisite are front-loaded, and every sentence carries information (metering, retry key, safety fields, boundaries). It is dense rather than wasteful, though the run-on sentences pack several distinct behaviors together without visual breaks.

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 an output schema already exists, the description needn't explain return values, and it covers the important gaps: prerequisites, metering, idempotency, and scope boundaries. Only the required 'item' payload semantics remain unaddressed for a fairly complex nested tool.

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 must carry the load. It adds strong meaning for request_key (fresh UUID, reuse on retry, persistence) and use_existing_allowance (confirmation before consuming allowance), but says nothing about the required nested 'item' object or its category/brand/model/specs fields, leaving that half of the parameters undocumented.

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 gives a specific verb and resource: 'request a maintenance guide for the appliance details and question the user supplied.' It also draws a boundary ('does not read on-device appliances or schedule tasks'), though it never names the sibling tools get_connected_installation or get_saved_guide_request, so cross-tool routing relies on inference.

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?

It states the precondition (a linked Pro installation), a procedural instruction ('Ask for confirmation before using existing Pro allowance'), and retry guidance ('reuse it for retries'). It is clear about usage context, but stops short of naming the alternatives an agent should pick instead.

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