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

The annotations declare destructiveHint=true, so the agent already knows this is a write operation. The description adds that it creates a task/event but does not disclose additional behaviors like required permissions, idempotency, or side effects. It does not contradict the 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?

Two sentences, front-loaded with the action and key constraint. Every word is informative, and no space is wasted.

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 create tool with 11 parameters and no output schema, the description provides the essential usage pattern and references the REST endpoint. It does not explain return values or errors, but the schema and annotations cover the rest adequately.

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 covers 100% of parameters, so the baseline is 3. The description adds strategic value by highlighting 'subject' as required and suggesting the optional linking to deal/person/org plus type/date/time, which helps prioritize the most important fields.

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 clearly states the tool 'Create a new activity (task/event)' with specificity, and distinguishes it from sibling read tools such as pipedrive_list_activities. The REST endpoint is also provided, reinforcing the action.

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 description gives clear context on how to use the tool (required subject, linking to deal/person/org, setting type/date/time) and implies it is for creating rather than listing activities. However, it does not explicitly mention alternatives such as pipedrive_list_activities or pipedrive_add_note.

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