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 only states the action ('log') without explaining permissions, whether it creates a Salesforce task or activity, idempotency, or what happens if the call already exists. This is a significant gap for a write operation.

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 two short sentences, achieving maximum conciseness without redundancy. Every word contributes to the purpose and usage context. It is well-structured and front-loaded.

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?

Given the tool's complexity (3 parameters, no output schema, no annotations), the description is too sparse. It does not explain parameter semantics, return values, or edge cases, leaving the agent under-equipped to invoke the tool correctly in a real sales workflow.

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 3 parameters with 0% description coverage, and the tool description provides no additional meaning for 'note', 'subject', or 'relatedId'. An agent has no guidance on what values to supply or what 'relatedId' refers to (likely a Salesforce record ID, but unstated).

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 action ('Log a call or meeting') and the resource ('Salesforce'), using a specific verb that distinguishes it from sibling tools like sf_create_task or hubspot_log_note. The phrase 'Use after any sales call' further clarifies its intended function.

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?

Description provides a clear usage context: 'Use after any sales call.' This implies when the tool should be used, but it does not explicitly reference alternative tools or state when not to use it. Still, it is sufficient for a simple logging action.

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