list_applications

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

With no annotations, the description must carry the full burden. It discloses key behavior: list ordering (newest first) and optional filtering by status. It does not mention any other behavioral traits such as pagination, limits, or side effects (though as a list operation, side effects are unlikely). The description provides basic transparency but no deeper detail beyond what the name implies.

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 a single sentence that front-loads the primary purpose, then adds two qualifiers (optional filter and ordering). Every word contributes meaning, with no redundancy or filler. It is appropriately sized for the tool's simplicity.

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?

Given the tool's low complexity (one optional parameter, output schema provided), the description covers the core purpose, the filter behavior, and result ordering. The output schema likely documents the return shape, so the description need not repeat that. The only missing element is explicit usage guidance versus sibling tools, but the overall picture is quite complete for a listing read operation.

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 no schema description, and the schema coverage is 0%. The description adds semantic meaning by stating that 'status' is an optional filter. However, it does not explain allowed values, the meaning of an empty string default, or the behavior when omitted. The description partially compensates for the schema gap but not completely.

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 states the tool's function with a specific verb and resource: 'List job applications'. It adds the optional status filter and the ordering 'newest first', which distinguishes it from sibling mutation tools like add_application and update_status. The purpose is unambiguous and self-contained.

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 implies this is the tool to use for viewing job applications, with optional status filtering. However, it does not explicitly mention when not to use it or how it relates to alternatives like pipeline_summary or get_pending_followups. There is no exclusionary guidance, so the usage context is clear but under-specified.

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