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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add useful context beyond the schema: the permission requirement (crm:write), the required 'note' field, and the return behavior (created resource with absolute URL). However, it does not disclose error behavior, validation rules, side effects, or what happens when optional fields like deal_id or activity_type are omitted, leaving some transparency gaps.

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 three short sentences with no waste. It front-loads the core action ('Creates a activity'), then quickly covers required fields, permission, and return value. It is appropriately sized for a tool of this complexity, though a minor grammatical error and lack of structure (e.g., bullets) prevent a perfect score.

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 4-parameter create tool with no annotations and no output schema, the description gives the essential facts: purpose, permission, required field, and return shape. It does not mention that organization_id is also required (only 'note' is highlighted), nor does it explain how activity_type or deal_id should be used. Given the sibling naming pattern, it could also clarify the tenant-vs-platform distinction more explicitly, so it is minimally adequate but not fully complete.

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. The description adds minimal parameter meaning beyond the schema: it highlights 'note' as required. It does not clarify the expected format, allowed values, or relationships among parameters such as deal_id or activity_type, so it neither raises nor lowers the baseline. The schema's own descriptions are extremely terse but present.

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 states a clear verb ('Creates') and a specific resource ('a activity in the tenant CRM'). The 'tenant CRM' qualifier helps distinguish this tool from the platform_crm_activities_create sibling, though it stops short of naming that alternative explicitly. Minor grammar issue ('a activity') does not obscure meaning.

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 implies the tool is for creating activities within a tenant CRM, and it states a prerequisite ('Needs crm:write on the organization'). However, it does not mention when to prefer this over sibling tools like commsharbor_crm_activities_update or platform_crm_activities_create, nor does it state when not to use it. The usage context is clear but no exclusions or alternatives are given.

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