list_applications

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

With no annotations, the description carries the full burden. It discloses an authentication requirement (HH_ACCESS_TOKEN) and hints at pagination behavior via (page/per_page/order_by), but does not state that the operation is read-only, describe the response shape, or mention rate limits or error behavior. Verb 'List' implies read-only, but the disclosure is minimal.

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 short sentences, front-loaded with the core purpose, then the auth note. The parenthetical parameter list is mildly redundant with the schema but adds a useful cue that pagination and ordering options exist.

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?

The description adequately states what the tool lists and the required authentication. However, with no output schema and no annotation coverage, the description could be more complete by mentioning the response format (compact summary vs. raw), defaults for pagination, or any access restrictions beyond the token.

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 schema description coverage is 100%, so parameters are fully documented there. The description adds little beyond echoing page/per_page/order_by alerting the agent to the key optional parameters, but does not provide new semantic meaning for any 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 uses a specific verb ('List') and resource ('applications/responses') and adds scope ('in a negotiation collection for a vacancy'). This distinguishes it from siblings like 'get_application' (single resource) and 'list_application_collections' (lists collection IDs, not applications).

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 provided about when to use this tool versus alternatives, no exclusions, and no mention of how it relates to similarly scoped tools like get_application or list_application_collections. The agent must infer the use case from the name and schema.

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