get_stock

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

Discloses the return fields (itemCode, itemName, currentQty) and implies a read-only operation, but does not detail error handling or edge cases; still adds value beyond missing annotations.

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?

Three concise, well-structured sentences that deliver key information immediately without redundancy.

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?

Covers purpose, required input, relationship with sibling tool, and return fields; no output schema exists, so description compensates adequately for a simple query 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 already covers the one parameter with a description; overall description reinforces its purpose and how to obtain it via search_items, adding useful context.

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 clearly specifies the action (queries current stock quantity) and the resource (specific item), and distinguishes itself from sibling 'search_items' by indicating a prerequisite workflow.

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?

Provides explicit guidance to first use search_items to find the item ID, setting clear context for use but does not explicitly mention when not to use.

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