set_calc_item_ordinal

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

No annotations are provided, so the description carries full burden. It discloses that the ordinal controls display order and that lower values show first, which is useful. However, it does not mention permissions, side effects on other items, or whether changes are saved immediately. Thus a score of 3 is warranted.

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?

A single sentence with no filler words. It front-loads the action and immediately explains the meaning of ordinal.

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?

The description explains the effect and meaning of the ordinal but does not address when this tool is preferable to update_calculation_item or what errors might occur. For a simple setter with no output schema and no annotations, it covers the essential domain info but lacks guidance on prerequisites and edge cases, hence 3.

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?

The schema already describes 3 of 4 parameters (table, ordinal, itemName) at 75% coverage. The description adds the conceptual link that the ordinal belongs to a calculation item within a group, but it does not add new parameter-level details beyond the schema. The ordinal semantics are almost identical in both, so baseline 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 uses the specific verb 'Set' and identifies the exact resource: 'a calculation item's Ordinal' and its purpose as 'display/sort order within the calculation group'. This clearly distinguishes it from other calc item tools like add/delete/update_calculation_item.

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?

It states the context ('display/sort order within the calculation group') and implies when to use it, but it does not explicitly mention alternatives or when not to use it. The context is clear enough for a 4, but not a 5 due to lack of explicit sibling differentiation.

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