Get Applicant

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

With no annotations, the description carries the full safety/behavior disclosure burden. It does add context by noting that the response includes job applications with specific attributes, but it does not state whether the operation is read-only, what happens if the applicant is not found, or any permission requirements. This is adequate but lacks richness.

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 concise sentence (~20 words) that front-loads the primary purpose ('Get a single applicant') and efficiently includes key details about lookup and returned data. There is no extraneous or redundant content.

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 get-by-id tool with one parameter and no output schema, the description is fairly complete. It explains the resource, lookup key, and scope of returned data (applications with stage, scores, flags). Minor omissions like error handling or exact matching behavior are not critical given the tool's simplicity.

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 100% (the single parameter applicant_id is described as 'The unique applicant ID, or the applicant's email address'). The description essentially restates this, adding no new meaning or format details, so baseline 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 clearly states a specific verb ('Get') and resource ('a single applicant'), and further specifies the lookup by 'unique ID or email address' and the inclusion of 'job applications with stage, scores and flags'. This distinguishes it from siblings like list_applicants (multiple) and get_application (different resource).

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 when to use the tool (when a single applicant's details, including applications, are needed) but does not explicitly mention alternatives or exclusions. For example, it doesn't say 'for multiple applicants, use list_applicants', but the context is clear enough.

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