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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description adds a genuine behavioral disclosure: 'The attachment is never requested,' which prevents the agent from expecting attachment data. It stops short of covering return format, pagination, or auth, so a 3 is appropriate.

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?

Three compact sentences with the resource and its contents front-loaded, followed by the negative disclosure and the endpoint. Every clause is informative, though the trailing 'POST /api/v1/getglbatch' is of marginal value to an agent already given structured fields.

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 single-parameter, read-only tool with a 100% covered schema, the description substitutes well for the absent output schema by enumerating the line fields returned. Nothing critical to invoking it 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 coverage is 100% and the schema itself documents the id pattern and even points to the source (GLBId from merit_list_gl_batches). The description adds no additional parameter meaning, so baseline 3 applies.

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) and resource (general ledger batch) and enumerates the nested contents (debit/credit lines with account, memo, department, tax, amounts). The singular 'One general ledger batch' implicitly distinguishes it from the plural merit_list_gl_batches sibling, though it doesn't name that sibling explicitly.

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?

Usage is implied by the singular scope (fetch one batch by id, versus listing batches), but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer the list-vs-detail relationship from the sibling tool names.

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