get_purchase_register

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safe/read-only nature. The description adds context that the result is a monthly summary rather than raw voucher data, which is useful behavioral information. But it doesn't elaborate on return format, pagination, or other operational behavior. With annotations present, this modest addition merits a 3.

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, well-structured sentence that front-loads the core action and resource, followed by the summary nature and a helpful sibling reference. No wasted words or redundant schema repetition.

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 simple two-parameter read-only tool with no output schema, the description gives the essential behavior: it retrieves a month-by-month Purchase Register for a date range. The output nature is briefly described, and the 'same design as get_sales_register' reference helps agents infer expected structure. Some return-field details are absent, but the tool's simplicity and annotations keep this adequate.

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 input schema fully describes both parameters ('from' and 'to') with format 'DD-MM-YYYY', so description coverage is 100%. The description adds only the general notion of a date range, which adds no meaning beyond the schema. Baseline 3 is appropriate.

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 states the action ('Get'), the specific resource ('Purchase Register from TallyPrime'), and defines the output ('a month-by-month summary of Purchase voucher activity'). It also references the sibling tool get_sales_register, reinforcing its identity and distinguishing it as the purchase-specific analog.

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 description implies when to use the tool: when a Purchase Register summary for a date range is needed. However, it does not explicitly state when not to use it or compare it to other register tools beyond noting the same design as get_sales_register. This leaves usage guidance largely inferred rather than explicit.

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