ashby_get_application_form_submission

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. The description adds valuable context about the nature of the returned data (candidate's written answers) and the response fields (application_id, candidate_name, job_title, form_responses), which goes beyond the annotation. It does not disclose potential edge cases (e.g., empty form), but for a read-only tool this is adequate.

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 efficient and well-structured: the first sentence states the core purpose, the second provides usage guidance, and the third lists the response fields. Each sentence adds distinct value with no redundancy or filler.

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 read-only tool with one parameter and no output schema, the description is complete. It explains what data is returned, gives usage context, and differentiates from siblings. There is no missing information an agent needs to call it correctly.

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 input schema already provides a full description for the single parameter (application_id), so schema coverage is 100%. The description reinforces that it fetches responses 'for a specific application' but adds no new syntax or format details. Baseline 3 is appropriate since the schema carries the semantic weight.

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'), the resource ('application form responses'), and the scope ('for a specific application'). It explicitly differentiates from sibling tools by clarifying it returns the candidate's submitted written answers (screening questions, cover letter, etc.), which distinguishes it from get_application_details and get_resume.

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 provides explicit when-to-use guidance: 'Use this to read what a candidate actually wrote in their application.' It also names preceding tools ('Use after ashby_list_candidates_for_job or ashby_get_application_details') and the goal ('evaluate a candidate's application content'), giving clear context and routing.

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