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

Annotations already declare write/destructive/non-idempotent/open-world, so the bar is lower. The description adds genuinely new behavioral context beyond those flags: that Teamgate may send reminders to the owner (an external side effect) and the underlying POST /events endpoint. It does not address duplicate creation, which matters given idempotentHint=false.

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 tightly packed sentences with zero filler; the 'WRITE:' prefix front-loads the operation class and the endpoint is appended as a useful trailer. Slightly dense but every clause carries information.

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 create tool with no output schema, the description covers the nature and side effects of the call but omits required-field expectations, failure behavior, and what is returned (e.g., the new activity id used by teamgate_get_activity). Adequate but with clear gaps for a mutation entry point.

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%, with per-field descriptions and constraints, so the schema carries the parameter burden. The description's 'optionally linked to leads, companies or deals' merely restates lead_ids/company_ids/deal_ids without adding format, limits, or interaction rules. 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 specific verb and resource ('create a task, call or appointment') and enumerates the type enum values, so the agent knows exactly what is produced. Implicitly distinguishes from the get/list siblings by the create verb, but never names a sibling for explicit contrast.

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?

There is no when-to-use guidance: nothing says when to create an activity versus using teamgate_add_note or teamgate_update_* tools, and no prerequisites (auth scope, owner requirements) are given. The linking mention hints at context but does not route the agent between alternatives.

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