get_stock_move_detail

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

With no annotations provided, the description carries the disclosure burden. The verb 'Return' conveys a read-only retrieval behavior, and 'diagnostic fields' hints at the kind of data included. It does not mention auth requirements, missing-ID behavior, or side effects, but for a simple get operation the read-only nature is adequately implied.

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 description is one sentence, front-loads the action ('Return'), and contains no filler. Every word contributes to identifying the tool's purpose.

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 detail-lookup tool with an output schema available, the description is nearly complete: it identifies the resource and scope. It could be more explicit about what qualifies as 'principal and diagnostic fields,' but the output schema covers the return shape.

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% and the description does not explain move_id beyond implying a single stock move is targeted. The parameter name and integer type are reasonably self-explanatory, but the description adds no semantic value beyond the schema.

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 uses the specific verb 'Return' and the resource 'one stock move,' making it clear this is a single-record detail lookup. It distinguishes itself from siblings like search_stock_moves and find_non_done_moves, though 'principal and diagnostic fields' is somewhat vague about exactly what is returned.

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 phrase 'for one stock move' implies this is the tool to call when a specific stock move's detail is needed. However, it provides no explicit guidance about when to use it instead of search_stock_moves, find_non_done_moves, or other move-related siblings.

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