Get furniture info

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that results contain fire data and fuel (not just geometry), but says nothing about behavior on an unknown furniture_id or whether results are cached/static catalog data.

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?

One short, front-loaded sentence with no filler, and the parenthetical payload list is informative rather than redundant. It is efficient, though it stops short of the routing sentence that would have made it maximally useful.

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 single-input read tool with full annotations and no output schema, the description is nearly complete: it identifies the resource and sketches the returned fields. Adding the lookup prerequisite (from list_furniture_catalog) would close the remaining gap.

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 single param already carries examples ('single_bed', 'sofa_3seat'), so the schema does the heavy lifting. The description adds no format or validity detail beyond what the schema provides; baseline 3 applies.

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 ('Get detailed information') and resource ('a specific furniture item') and even enumerates the payload (dimensions, fire data, fuel), so an agent knows exactly what comes back. It does not explicitly name the sibling list_furniture_catalog, so the differentiation from the catalog tool is only implied.

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 singular 'a specific furniture item' implies this is the drill-down counterpart to list_furniture_catalog, but the description never states when to use it versus the catalog or that an ID must be obtained first. Usage is inferable but not spelled out.

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