list_applications

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

With no anotations, the description carries the burden of disclosing behavior. It conveys that this is a non-mutating read operation and describes the kind of data returned. It does not mention side effects, persistence semantics, or ordering/pagination, but for a list tool the core behavior is adequately suggested.

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 short and front-loaded with concrete information. The metaphor 'long-term memory' adds some flavor but is not essential; overall every sentence earns a place.

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 list with two optional parameters and no output schema, the description gives enough to understand the general return content. It does not explain the filtering behavior of status or the meaning/effect of limit, leaving the agent to infer from the schema.

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 0%, so the description should compensate. It nore mentions 'status' as a field in the returned history, which sheds some light on that parameter, but it does not explain that status functions as a filter, and it says nothing about the limit parameter.

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 identifies the resource ('Application history') and the specific data it contains (job, company, status, dates), and gives scope ('everything already applied to'). It does not explicitly name sibling alternatives, so it stops short of full differentiation.

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?

No guidance is given on when to choose this tool over related siblings like check_applied, get_status, or record_application. The phrase 'long-term memory' implies a read/history use case, but no conditions or exclusions are stated.

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