fetch_activity_log

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

No annotations are provided, so the description carries full burden. 'List activity log' implies a read operation, but it doesn't disclose important behavioral traits: whether this requires authentication, what format the log entries have, if there are rate limits, whether results are paginated by default, or what happens with invalid parameters. The mention of 'Optional per_page, page, user_id' hints at pagination and filtering but doesn't explain behavior.

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 appropriately concise at 8 words. It's front-loaded with the core purpose ('List activity log') followed by parameter hints. Every word earns its place, though it could benefit from slightly more structure (e.g., separating purpose from parameters with punctuation).

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 3 parameters with 0% schema coverage, no annotations, and no output schema, the description is incomplete. It names parameters but doesn't explain their use, doesn't describe the return format, and provides no behavioral context for a data retrieval tool. For a tool that likely returns structured log data, this leaves significant gaps for an AI agent.

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 description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'Optional per_page, page, user_id' which names the three parameters but adds minimal semantics: 'per_page' and 'page' suggest pagination, 'user_id' suggests filtering. However, it doesn't explain expected formats (numeric vs string), valid ranges, or how filtering works. With 3 undocumented parameters, this is inadequate compensation.

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 states 'List activity log' which provides a basic verb+resource combination, making the purpose understandable. However, it's vague about what 'activity log' contains and doesn't distinguish this from other list/fetch tools among the 50+ siblings. It's better than a tautology but lacks specificity about scope or content.

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 provides no guidance on when to use this tool versus alternatives. With many other fetch_* tools (fetch_assets, fetch_stories, fetch_users, etc.), there's no indication of what makes 'activity log' distinct or when it should be preferred over other data retrieval tools. No exclusions or prerequisites are mentioned.

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