get_lead_logs

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

No annotations are provided, so the description carries the full burden. It only states 'Get activity logs', implying a read-only operation, but does not disclose any behavioral traits such as pagination, rate limits, error handling for invalid leadId, or whether the logs are real-time. Limited transparency.

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 (14 words) that is front-loaded with the action and resource, and includes illustrative examples. No wasted or redundant words.

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 simple single-parameter tool with no output schema, the description is reasonably complete. It defines the input (leadId) and the nature of the output (activity logs with examples). It could be improved by specifying the output structure or any limitations, but it is adequate for basic selection.

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 coverage is 100% (leadId with description 'The lead ID'). The description adds no additional meaning beyond the schema; it merely restates that the tool is for a specific lead. Hence baseline 3, no added value.

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 verb 'Get' and the resource 'activity logs for a specific lead', with examples of log types. However, it does not explicitly differentiate this tool from similar siblings like 'get_lead_conversations', which also retrieves lead-related data.

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 usage when activity logs are needed, but provides no explicit context on when to use this tool versus alternatives (e.g., get_lead_conversations) or any prerequisites. No guidance on when not to use it.

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