get_item_position

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the name—it does not disclose what happens if the position is not found, whether it returns null or errors, or any other runtime behavior. Since the description is merely a restatement of the tool name, it adds minimal value beyond 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?

The description is extremely short but under-specified. While it has no wasted words, it also provides no useful information beyond the tool's name, essentially repeating the name. This is under-specification rather than effective conciseness.

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?

With no output schema and a description that only says 'Fetch an item position', the description is not complete enough to prepare the agent for what the tool does, what it returns, or the relevance of the document type parameter. The schema covers parameter meanings, but the overall purpose and expected behavior remain underexplained.

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 the parameters are fully documented in the schema. The description adds no additional semantic nuance beyond what is already in the schema, which is acceptable for a baseline score of 3.

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 'Fetch an item position' uses a specific verb and resource, clearly distinguishing it from sibling tools like get_discount_position or get_text_position. However, it does not elaborate on what an item position is or that it belongs to quotes, orders, or invoices, which would add clarity.

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?

No guidance is provided on when to use this tool versus alternatives like list_item_positions or get_discount_position. The description does not mention that it retrieves a single specific position by ID or any context about the document type, leaving the agent without usage direction.

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