Prior applications

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

With no annotations, the description carries the full burden and aptly declares 'Read-only', telling the agent this is a safe, non-mutating operation. It also notes the data is a 'local' ledger. It doesn't specify edge cases (e.g., empty history) or return format, but for a simple read this is solid disclosure.

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?

Two tight sentences, front-loaded with the core purpose, then usage guidance and a behavioral flag. Every sentence earns its place with zero filler.

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?

Complete for a low-complexity tool (one optional param, no output schema). It covers purpose, use case, and read-only behavior. The only gap is that the return contents aren't described, but for this simple ledger-read it's mostly sufficient.

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%, so the single optional parameter is already fully documented ('Filter to one employer; omit for the full history'). The description adds no parameter-level detail beyond this, which lands at the 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?

States a specific verb and resource ('Read the local application ledger') that clearly distinguishes it from siblings like search_roles (searching postings) and check_sponsor (visa status). The purpose is immediately actionable and unambiguous.

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 says when to use it ('Use it before applying to avoid duplicate submissions to the same employer, and to see what has already been tried'). It gives clear context, though it doesn't name sibling tools as explicit when-not-to-use alternatives.

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