get_application

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

No annotations are provided, so the description carries the full burden. It mentions 'Get' and 'Returns' but does not explicitly state that it is a read-only operation, any required permissions, or potential error conditions. Minimal behavioral disclosure.

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 short and well-structured with separate Args and Returns sections. It is front-loaded with the purpose, and every section earns its place, though the Args details are tautological.

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 getter, the description provides the essential purpose, parameters, and return type. However, given the absence of annotations and schema descriptions, it lacks context on error handling, authentication, or the exact structure of the returned dictionary, making it minimally sufficient but not comprehensive.

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 0%, so the description must compensate. The Args section repeats the parameter names and says 'The applicant ID' and 'The application ID', which adds no meaning beyond the schema's property names. It does not explain the relationship between the two IDs or any value constraints.

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 it retrieves a specific application by ID, using a specific verb and resource. It distinguishes from list-type tools, though it doesn't explicitly differentiate from other get_ tools or clarify the need for both applicant_id and application_id upfront.

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 on when to use this tool versus alternatives such as list_applicant_applications or update_application. The description only states what it does, not when to choose it.

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