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

Annotations supply only destructiveHint=true and a title, leaving the description to add behavioral context. 'WRITE' and 'POST /note' restate the obvious write nature rather than disclosing anything new, such as whether the note appears on the constituent timeline, permission requirements, or whether it is editable afterwards. No contradiction with the annotations, but minimal added value.

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 fragments are front-loaded and waste no words, but 'Bloomerang: POST /note' is endpoint trivia that gives the agent no decision-relevant information and partly duplicates the WRITE prefix and the tool name.

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 three-parameter write with full schema coverage and no output schema, the description is just minimally adequate. It omits any expected outcome (e.g., created note id) and any note about the surprising destructiveHint=true annotation on what reads like an append operation.

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 all three parameters (including the important disambiguation that constituent_id is the API Id, not the AccountNumber) are already documented. The description adds no field-level meaning beyond that, which is the expected baseline when the schema does the work.

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 gives a clear verb+resource ('add a note to a constituent's record') that an agent can act on immediately. It does not differentiate from the sibling bloomerang_list_notes or bloomerang_create_interaction, but the write semantics are unambiguous.

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 guidance on when to use this versus bloomerang_create_interaction or other timeline-writing siblings, and no prerequisites or exclusions stated. The reader must infer usage entirely from the tool name.

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