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

The annotation set only declares destructiveHint=true, so the description carries the remaining burden. It reveals the operation is a POST (a write), which is consistent with the annotation, but says nothing about whether the note is customer-visible, whether it notifies anyone, whether it can be edited/deleted, or what permissions are required.

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?

Two short sentences, purpose front-loaded, nothing redundant. The trailing 'Housecall Pro: POST /jobs/{job_id}/notes' is mildly useful for API-level traceability but is closer to filler than essential behavior.

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 two-parameter write tool with no output schema this is nearly adequate, but a mutation flagged destructiveHint=true warrants at least a word on side effects or reversibility that is absent here.

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?

Both parameters (job_id, content) are fully documented in the schema at 100% coverage, so the schema does the heavy lifting. The description adds no format, length, or tagging semantics beyond what the schema already provides, which is the baseline case.

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 states a specific verb and resource ('Add a text note to a job'), and no sibling tool touches job notes, so it is trivially distinguishable from the create/get/list/update family. An agent knows exactly what this does.

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?

There is no when-to-use framing, no when-not-to-use, and no named alternative. Usage is only implied by the name and the single sentence; nothing helps the agent decide between this and, say, updating a job's fields.

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