Get Dla Balance

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context by noting the tool shows balance, transactions, and section 455 tax warnings, which is beyond the annotations. It does not introduce any contradictions and provides useful behavioral specifics.

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 two sentences with no filler. It front-loads the main action and resource, then adds the key output details. Every word earns its place, and it is appropriately short for a simple read-only tool.

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?

Given there is no output schema, the description provides essential output context: balance, transactions, and tax warnings. It also implies the return of a list of transactions via the 'limit' parameter. While it does not detail exact fields or pagination, the description is adequate for a tool with a single optional parameter and read-only annotations.

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 description covers the single 'limit' parameter fully with 'Max number of transactions to return (default 10)'. The tool description does not add any additional meaning for this parameter, so it meets the baseline of 3 given high schema coverage.

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 states a specific verb and resource: 'Get the Director's Loan Account (DLA) balance and recent transactions.' It also explains the output's significance (whether director owes company or vice versa) and mentions a key detail (section 455 tax warnings). This clearly distinguishes it from other balance tools like get_balance or get_trial_balance, which target different accounts.

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 usage context through its name and purpose (DLA queries) but does not explicitly state when to use this tool over alternatives, nor does it list any exclusions or alternative tools. An agent can infer usage, but the guidance is not explicit.

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