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

Goes meaningfully beyond the annotations by disclosing a side effect the caller cannot see in the schema: 'The type may move the lead's stage or temperature.' It also describes a return-value signal ('The answer says next_step_required when the lead now has no follow-up'), which is valuable given there is no output schema. With destructiveHint=false already declared, this added mutation context is exactly what the description should carry.

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 sentences, front-loaded with the core action, then side effects, then the response signal — a sensible information order with no filler. Slightly more compact phrasing could tighten the final sentence, but nothing is redundant.

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 6-parameter mutation tool with no output schema, the description covers the essential gaps: prerequisites (open lead), hidden side effects (stage/temperature changes), and the shape of the response flag. What remains thin is the distinction from adjacent write tools, which an agent would still have to resolve from sibling names alone.

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 six parameters are already documented, including the activity_type_id pointer to desk_list_activity_types. The description mentions the optional outcome and note in passing but adds no format or constraint detail beyond what the schema states, 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 concrete verb and resource — 'Logs an activity of a type ... on an open SautiDesk lead' — with parenthetical examples ('a site visit, an offer sent') that make the resource tangible. It implicitly separates itself from desk_add_lead_note and desk_set_activity_outcome by scoping the write to the activity log, but never names those siblings explicitly.

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?

The phrase 'on an open SautiDesk lead' encodes a real prerequisite (the lead must be open), which is a useful selection condition. However, there is no explicit when-to-use versus when-not, and no pointer to desk_set_activity_outcome for setting outcomes on activities that already exist, leaving the agent to infer the boundary.

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