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

Annotations already declare destructiveHint=true, and the description adds real context beyond them: the POST /api/v0/activities endpoint, form-encoded body, and the {meta, response} return envelope. This is solid, but calling itself the 'highest-value safe write' sits in tension with destructiveHint=true and could understate risk to an agent.

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?

Front-loaded with the mutation warning and compact at four short sentences. The 'highest-value safe write' clause is marketing filler that does not earn its place, but overall it is tight.

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 9-parameter tool with no output schema, the description covers the endpoint, encoding, return shape, and the required target pairing. It does not explain the optional fields (fields, visibility, owner_type), but the schema covers those.

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 parameter is already documented. The description only restates the against_type + against_id pairing and their requiredness, adding little meaning the schema does not already carry — baseline 3.

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 names a specific verb (logs) and resource (an activity: note, email, call, or meeting) and states the object it targets. This is clearly distinguishable from siblings such as create_task, create_contact, or create_company.

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?

It provides a concrete use case ('add a note/comment to a job or company') and frames the tool as the preferred lightweight write. However, it never says when to choose it over siblings (e.g. create_task or the generic accelo_request), so usage is only implied.

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