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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the mutation/safety profile is covered structurally. The description adds the POST endpoint and the meaningful constraint that at least one parent id must be supplied, but says nothing about permissions, retention, or whether the note is visible to other users.

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 tight clauses, front-loaded with the operation class ('WRITE'), then what is written, then the binding constraint. No filler and no restatement of 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?

For a six-parameter mutation tool with no output schema, the description covers the essentials: what gets created, where it attaches, the parent-id requirement, and the endpoint. Minor gaps remain around side effects (does adding a note touch deal activity timestamps or notifications) and error behavior when no parent id is passed.

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 coverage is 100%, so the per-field documentation is already handled and baseline would be 3. The description goes beyond the schema by stating a cross-field requirement that the schema omits: the schema requires only 'content', yet the note must be attached to at least one of deal_id, person_id, or company_id. That is genuine added semantics.

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 a note/activity') and resource, plus the attachment scope (deal, person, or company). This clearly separates it from read siblings like pipelinecrm_list_notes and pipelinecrm_get_note, and the 'WRITE:' prefix signals the operation class immediately.

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?

Usage is implied by the write verb and the attachment targets, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., 'to read existing notes use pipelinecrm_list_deal_notes'). The only directive given is an invocation constraint, not selection guidance.

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