get_recent_activities

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

The description states it's a read operation returning a structured object, but with no annotations, it doesn't disclose traits like read-only safety, error handling, or side effects. It provides basic transparency but lacks depth expected for a tool without annotation support.

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 extremely concise with no wasted words, front-loading the purpose and directly stating the argument and return value. Every sentence is essential.

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 simplicity (one parameter, output schema exists), the description covers the basics. However, it omits potential context like result limits or ordering, leaving some gaps for a complete understanding.

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 coverage, the description adds meaning by clarifying contact_id is the numeric id, beyond the schema's type and title. However, it's minimal and obvious, so it only reaches baseline adequacy.

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 tool retrieves recent activities (calls, meetings, emails) for a contact, using a specific verb and resource. It distinguishes from sibling tools like get_contact or get_deal by focusing on activities, though it doesn't explicitly contrast with alternatives.

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 on when to use this tool versus alternatives. The description implies usage when you need recent activities for a contact, but offers no exclusions or context for when not to use it, making it minimally helpful for an AI agent.

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