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

Annotations already convey that this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the convenience-wrapper relationship to create activity but does not disclose detailed side effects, permissions, or return behavior. No contradiction with annotations.

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 a single, focused sentence of about 17 words. It front-loads the core purpose and packs in the activity types, target objects, and wrapper relationship without any filler or redundancy.

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 tool with four optional string parameters and no output schema, this description provides sufficient context for selection and basic invocation. It could be more explicit about parameter defaults or required combinations, but the current level is adequate and not severely incomplete.

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?

The schema has 0% description coverage, but the description compensates by mapping type to the allowed values (note/call/email/meeting/task) and associating deal_id/contact_id with deal/contact. It does not explicitly define body, though that is largely self-evident from the context of logging an activity.

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 specific action 'Log an activity' and enumerates the activity types (note/call/email/meeting/task) and targets (contact/deal). It distinguishes itself from siblings by noting it is a 'convenience wrapper over create activity,' setting it apart from generic create or update tools.

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 gives clear usage context by framing the tool as a convenience wrapper for logging activities, implying it should be used instead of lower-level activity creation. However, it does not explicitly name sibling alternatives or provide when-not-to-use guidance, so it falls just short of a 5.

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