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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states the action and endpoint, omitting any mention of side effects, required permissions, idempotency, or response behavior. It adds no context beyond the verb 'Create' already in 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, clear sentence that front-loads the action and includes the exact endpoint. Every word earns its place; there is no redundant information.

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?

The tool has a nested 'body' object with no schema details, no output schema, and no annotations. The description does not explain what constitutes a Lever note or how to structure the body, leaving a significant gap for an agent to invoke it correctly. The endpoint alone is insufficient for complete context.

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%, so each parameter is already documented. The description adds no additional meaning to the parameters, and the schema descriptions themselves are somewhat generic (e.g., body is 'JSON body to send to the documented Lever endpoint'), making this a baseline 3.

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 'Create a Lever note' with the exact REST endpoint, specifying both the action (create) and the resource (note). It effectively distinguishes this from sibling tools like update_opportunity_note, delete_opportunity_note, and list_opportunity_notes.

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 usage is implied by the verb 'Create' and the endpoint path, but no explicit guidance is given for when to use this tool versus alternatives. There are no prerequisites, exclusions, or conditions mentioned beyond the operation itself.

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