list_activities

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

With no annotations, the description carries the behavioral burden, and it does well by explicitly stating 'Read-only' and describing the JSON return shape including total and an activities array with fields. It does not mention pagination, error cases, or auth requirements, but for a simple list operation the disclosed behavior is adequate.

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 compact and well-structured: a plain-language summary first, then a clear Args section, then a Returns section. Every sentence adds information, and the read-only note is placed early where it matters most.

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 fully covers the three parameters, the purpose, the read-only nature, and the return format. Given that the tool has only one required parameter and the output schema is already available, nothing essential is missing for an agent to select and invoke 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?

Schema description coverage is 0%, so the description must compensate, and it does thoroughly. Each parameter is explained: album_id identifies the album, asset_id restricts to a specific asset, and activity_type accepts 'comment' or 'like' with omission meaning both. This adds meaningful semantics beyond the bare 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 that the tool reads comments and likes on a shared album or a specific photo within it. The phrase 'Use this to read what the people an album is shared with have said' is a specific verb-plus-resource statement that separates it from create/delete activity siblings.

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 gives clear guidance on when to use the tool: to read activity on an album or one of its photos. It does not explicitly name alternatives or state when not to use it, but the read-only framing and the focus on social activity make the intended context unambiguous.

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