list_applications

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

With no annotations, the description carries the full behavioral disclosure burden. It usefully discloses pagination and the return fields, but does not mention default limits, ordering, or potential side effects—though it is a list operation and thus implicitly read-only.

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 sentences with no filler: the first gives the action and resource, the second the return behavior. Everything present earns its place, and the key scoping phrase is front-loaded.

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 tool with three optional parameters and no output schema, this is reasonably complete: purpose, pagination, and return fields are covered. It could mention sorting or default page size, but the schema documents the parameters adequately.

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 baseline of 3 applies. The description does not add parameter-level insights beyond what the schema already provides; at most it complements the status filter by listing return fields.

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 job applications from Ascend') and names the returned fields, making it clearly a list operation. It distinguishes itself from siblings like get_application, which implies fetching a single application, and get_dashboard_stats/get_analytics_overview, which are analytics-oriented.

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 clearly indicates this is the tool for listing applications and notes pagination, placing it in a clear usage context. It does not explicitly state when not to use it or name alternatives, but the sibling names make those alternatives inferable.

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