hires_get_form

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

With no annotations provided, the description carries the full burden. It implicitly conveys read-only behavior via 'Get' and specifies the returned content (form details + questions with statuses). It does not explicitly state that it does not mutate data, but this is strongly implied by the verb. It adds useful detail beyond the name.

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 a single, front-loaded sentence that states the operation and key details ('Get form details including all questions with their statuses'). Every word earns its place; there is no filler or repetition.

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 with one parameter and no output schema, the description adequately explains the return value (form details with questions and statuses). It does not explicitly state the operation is read-only, but the verb 'get' implies it. It is complete enough for 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?

The only parameter 'id' is fully described in the schema ('Form ID'), providing 100% coverage. The tool description does not add additional parameter meaning, but the baseline for high schema coverage is 3, and the description's reference to 'form details' aligns with the 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 ('Get') and resource ('form details'), and adds a distinguishing detail ('including all questions with their statuses'). This clearly sets it apart from sibling tools like hires_list_forms (list vs. get) and hires_get_question (single question vs. form with all questions).

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 context is clear: use this to retrieve a single form's details, including its questions and their statuses. However, it does not explicitly mention when not to use it or point to alternatives (e.g., hires_list_forms for a list of forms), so it falls short of a 5 but provides unambiguous context.

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