marketo_get_lead_activities

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

No annotations provided; the description says it 'Get activity log' and 'Returns timestamped activity records' but does not disclose read-only nature, authentication needs, rate limits, or side effects, leaving transparency minimal.

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?

Two concise sentences front-load the main purpose and efficiently add filtering and pagination details without fluff.

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?

Despite no output schema, the description mentions 'timestamped activity records' but lacks detailed return format. For a tool with four parameters, it is adequate but not fully comprehensive.

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 100% schema coverage, the description adds value by providing examples for activityTypeIds (e.g., 1=Visit Web Page) and clarifying pagination use, going beyond the raw schema.

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 'Get activity log for a specific lead' with additional details on filtering and pagination, distinguishing it from sibling tools like lead creation or email cloning.

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 mentions filtering by activity type IDs and pagination, but lacks explicit when-not or alternative tools. Usage context is clear but not exhaustive.

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