get_reorder_status

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds substantial behavior beyond that: the tool filters the raw Tally report down to only reorder-configured rows, with concrete live evidence (a 10,770-item company producing a ~1.4MB all-null dump). It also discloses the empty-rows-with-note return convention, which is exactly the kind of edge-case behavior an agent needs to know.

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?

Purpose is front-loaded in the first sentence, and the sibling routing comes last, which is a sensible order. The middle sentence is long, and the live anecdote adds credibility but could be trimmed; still, every sentence contributes new information, so it earns a 4 rather than a 3.

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 2-parameter read-only tool with no output schema, the description compensates thoroughly: it lists the row fields, explains the filtering behavior, defines empty-result semantics, and routes to the appropriate alternative. Nothing an agent needs to call the tool correctly is missing.

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% with both from and to documented as DD-MM-YYYY dates, so the baseline of 3 applies. The description only adds that the report spans 'a date range,' which mildly reinforces parameter intent but provides no format or constraint detail beyond what the schema already gives.

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?

States a specific verb ('Get'), a specific resource ('Reorder Status report from TallyPrime'), and the exact scope ('stock items with a reorder level configured, and where their current quantity stands against it'). It also enumerates the per-row fields returned, so an agent knows precisely what this tool produces.

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 tells the agent when this tool is the right choice versus a sibling: 'use get_stock_summary for a plain quantity view of every item regardless of reorder setup.' It also defines when an empty result is a legitimate outcome ('no items have a reorder level configured at all'), preventing the agent from misreading a valid empty response as an error.

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