list_applications

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return format (chat-ready plain text), which is genuine context, and "List" implies a read-only operation. It says nothing about ordering, result limits, pagination, or whether all applications or only active ones are returned.

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?

One short sentence, front-loaded with the action and scope, with no filler. It is efficiently written, though brevity here edges toward under-specification rather than economy.

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?

An output schema exists, so return values need not be explained, and a zero-required-parameter list tool is inherently simple. Still, the definition leaves the agent guessing about valid status values and about when a specialized sibling is the better choice, which is incomplete for a tool sitting among several overlapping listers.

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 single parameter has 0% schema description coverage and no enum, so the description is the only source of meaning. It correctly conveys that filtering is optional and that the parameter filters by status, but it never indicates valid status values or whether an empty string means "no filter" — a real gap for a free-form string input.

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 ("List applications") and adds two defining traits: plain-text chat-ready output and optional status filtering. It does not name or contrast itself with overlapping siblings such as find_stale_applications or what_is_due_this_week, which is the only thing separating it from a 5.

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 only implied: an agent can infer this is the general-purpose lister and the status parameter narrows results. There is no explicit "use this when / prefer X instead" guidance, which matters here because three siblings (find_stale_applications, what_is_due_this_week) return overlapping subsets of the same data.

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