sf_recent_activities_by_lead

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

The description implies a read-only retrieve operation, which is transparent. However, it does not disclose the definition of 'recent', ordering, pagination, or required permissions. Since no annotations are provided, the description carries the full burden but only partially meets it.

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 sentence with no unnecessary words or redundancy. It is front-loaded and efficient.

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?

The description covers the basic purpose but omits details on return format, default behavior, error cases, and timeframe for 'recent'. Given the absence of output schema and annotations, more context is needed for an agent to use the tool correctly.

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?

With 0% schema description coverage, the description adds no value beyond the parameter names. 'leadId' and 'limit' are somewhat self-explanatory, but the description does not clarify their purpose, format, or behavior (e.g., what 'limit' controls). A brief explanation would improve usability.

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 ('retrieve') and resource ('recent tasks and events') and specifies association with a specific lead. However, 'recent' is vague and the description does not explicitly differentiate from sibling tools like sf_recent_activities_by_contact or sf_list_tasks_by_lead.

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?

No guidance is provided on when to use this tool versus alternatives such as sf_get_lead, sf_list_tasks_by_lead, or sf_activity_summary. The description lacks context about use cases, prerequisites, or exclusions.

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