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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful detail that this depends on an externally-resolved record ID, but says nothing about duplicate logging on retry (relevant given idempotentHint=false) or side effects on the CRM record.

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 sentences, no waste, with the action stated first and the prerequisite second. Nothing is padded or restated from the title.

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?

An output schema exists and all parameters are fully described, so return values and field meanings are covered elsewhere. The description supplies the one thing structured fields cannot: the ID provenance requirement. Only the retry/duplication behavior for a non-idempotent write is left unaddressed.

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 every one of the nine parameters is already documented in the schema, including the type values and date formats. The description adds no semantics beyond that and so sits at the baseline.

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 (log) and resource (note/call/meeting/task activity) and names the object it attaches to (person or company record in the customer's CRM). It implicitly separates itself from the lookup/add siblings it references, though it never distinguishes itself from update_crm_record, which is the nearest ambiguous alternative.

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?

Gives a hard prerequisite: the record must be one returned by find_person_in_crm, search_crm or add_person_to_crm, which tells the agent it must resolve an ID first. It stops short of stating when to choose this over update_crm_record or when not to log.

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