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

With no annotations, the description carries the full burden, but it only states that the tool creates an activity. It does not disclose side effects, required context, permissions, idempotency, or what data is returned.

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?

The description is one short sentence, but this is under-specification rather than effective conciseness. It front-loads the action with no supporting context that would help an agent invoke the tool correctly.

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?

A 4-parameter CRM tool with no output schema and no annotations needs more context than 'create CRM activity.' It does not explain what an activity represents, how activity_type should be valued, how deal_id relates to the activity, or what a successful creation looks like.

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 baseline is 3, but the parameter descriptions merely repeat the field names ('note', 'deal id', 'activity type', 'organization_id'). The long-form description adds nothing about parameter meaning or constraints, so it does not exceed the baseline.

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 the exact operation and resource: creating a CRM activity. It is clear enough to distinguish from the delete/get/list/update siblings, though it does not clarify how it differs from the similarly named platform_crm_activities_create variant.

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 guidance on when to choose this tool over alternatives such as commsharbor_platform_crm_activities_create or the update/list variants. The intended use is only implied by the verb and sibling naming, with no when-to-use or when-not-to-use conditions.

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