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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: the concrete consequence of non-idempotency (two records), the workflow side-effect, the error contract ('Invalid field values are rejected with the rule that failed'), and the underlying endpoint. It stops short of permission/auth requirements or rate limits, hence not a 5.

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?

Three compact sentences plus an endpoint, front-loaded with the WRITE marker and the create semantics, followed by the idempotency caveat, the side-effect warning, and the error contract. No sentence is 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 two-parameter mutation with full schema coverage and no output schema, the description covers creation semantics, duplicate risk, side effects, and failure behavior. The only remaining gap is what the call returns (e.g. the new record ID), which an agent creating a record would likely want; small but real omission.

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 the schema already documents both parameters in depth, including field-format quirks (arrays for select/point-to-record, email/currency/date shapes). The description adds no parameter-level detail beyond referring to 'the given type,' so the baseline 3 applies.

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?

States a specific verb and resource ('create ONE new record of the given type') plus the target system ('live Beacon database'), and implicitly contrasts scope with the singular-record nature versus sibling list/filter tools. An agent can distinguish this from beaconcrm_upsert_record or beaconcrm_update_record without opening any schema.

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?

Explicitly names the alternative tool and the condition that selects it: 'Not idempotent: calling it twice creates two records (use beaconcrm_upsert_record to avoid duplicates).' It also flags the collateral effect (workflows may run), which is decision-relevant before invoking a write.

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