container_lookup

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

Annotations already mark readOnlyHint=true and idempotentHint=true, so the core safety profile is covered. Description adds behavioral context by mentioning 'calculate loading' and 'list all types' when type is omitted, but doesn't elaborate on return format or potential pagination. Adequate but not extensive.

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?

Description is concise with only three short paragraphs, each earning its place. Purpose and use cases are front-loaded. No fluff or repetition. Efficient and well-structured.

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 6 parameters and no output schema, description covers both modes (specs and loading) and lists container types. However, it doesn't describe the output format or clarify how optional parameters like weight and quantity affect results. Leaves some gaps for a tool of this complexity.

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%, so baseline is 3. Description reinforces usage patterns ('Provide a container type for specs. Add item dimensions (l, w, h in cm) to calculate loading') but adds minimal new meaning beyond the detailed schema descriptions. Meets the baseline expectation.

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?

Description clearly states 'Get ISO shipping container specifications and calculate loading', specifying a verb and resource. Lists 10 container types and three distinct use cases, differentiating from sibling tools like cbm_calculator and pallet_fitting_calculator by offering combined specs and loading calculations.

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?

Explicitly begins 'Use this tool when you need to:' and lists three scenarios (get specs, pallet count, item loading). Provides clear context for when to use, but does not directly state when to use alternatives like pallet_fitting_calculator, leaving some room for ambiguity.

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