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

Annotations supply only destructiveHint=true and a title, so the description carries most of the behavioral burden. It states the write and the underlying endpoint (POST /activities) but says nothing about side effects on the activity feed, notification behavior, or reversibility - notable gaps for a mutating tool whose destructiveHint is the only annotation.

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 short sentences with the purpose front-loaded and no filler. The trailing endpoint reference is compact, though partly internal implementation detail rather than agent-facing guidance.

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 five-parameter create tool with full schema coverage and no output schema, the description covers purpose and the record_type_name default but omits any guidance on required-field effects, feed visibility, or the actor permission nuance that the schema does handle. Adequate but with clear gaps for a mutation.

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 all five parameters, including the record_type_name default. The description adds only a marginal pointer that alternate activity types come from account settings; baseline 3 is appropriate when the schema does the heavy lifting.

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 gives a specific verb and resource - adds a note/activity entry to a contact or job's activity feed - and specifies the target entity, which cleanly separates it from jobnimbus_create_contact, jobnimbus_create_job, and jobnimbus_create_task. An agent can identify the operation without opening the 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?

It explains that record_type_name defaults to Note and that alternative activity types come from account settings, which is useful in-tool guidance. However, it offers no when-to-use versus alternatives context (e.g., versus create_task or list_activities) and no prerequisites for the mutation, so guidance is only implied.

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