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

No annotations are provided, so the description carries the burden. It discloses that this is a get/read operation and that the application is attached to a candidate. However, it lacks details about permissions, error behavior, or the exact structure of the returned data, though it hints at the included analysis fields.

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 concise, consisting of two short sentences with the key information front-loaded. It avoids unnecessary detail and is easy to scan.

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 get tool with no output schema, so the description should provide some insight into the return value. The phrase 'for stage, job, and disposition analysis' suggests the response contains these fields, but it does not fully describe what the caller can expect. Adequate but could be more explicit about the full response contents.

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 high (80%), so the baseline is 3. The description adds context for the 'id' parameter by stating 'by application id', but it does not elaborate on 'include', 'query_json', or 'path_params' beyond what the schema already provides. Minimal added meaning.

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 action ('Get one candidate_application') and specifies the resource. It also differentiates from siblings by mentioning 'by application id' and the analytical context ('for stage, job, and disposition analysis'), which distinguishes it from tools like get_candidate.

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 gives a clear usage context ('for stage, job, and disposition analysis') indicating when this tool is appropriate. However, it does not explicitly exclude alternatives or mention when not to use it, such as when a candidate-level lookup is needed.

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