List Applications

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

With no annotations, the description carries the burden. It does disclose useful behavioral traits: ordering by soonest deadline and aggregating counts per status. However, it does not explicitly confirm read-only behavior, pagination, or what 'pipeline' fully includes, so coverage is partial.

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 one short fragment with no filler; both the ordering and the per-status count fact are useful. It is slightly ungrammatical, but that does not hurt comprehension.

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?

This is a simple list operation with one optional, fully documented parameter and an output schema available. The description adds the key context (sort order and count aggregation), which is enough for an agent to invoke it correctly.

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 only parameter, status, has 100% schema description coverage with the allowed values listed. The description itself adds little about the parameter, but the schema already provides the necessary meaning, so the baseline of 3 applies.

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 identifies the resource (the pipeline/applications) and adds concrete behavior: soonest deadline first and a count per status. It relies on the title for the explicit verb 'List,' and it does not contrast with any sibling, but the meaning is clear enough.

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?

There is no guidance on when to use this tool versus siblings like get_followups, track_application, or find_warm_paths. The usage is only implied by the name and the pipeline framing; no exclusions or alternatives are mentioned.

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