List Activity

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Show recent activity feed,' which doesn't reveal any behavioral traits such as permissions needed, rate limits, pagination, or what 'recent' means. This is inadequate for a tool with no annotation coverage.

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, efficient sentence ('Show recent activity feed.') with no wasted words. It's appropriately sized and front-loaded, making it easy to scan.

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 complexity (a list operation with one parameter), no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavior, return values, and usage context, making it insufficient for effective tool 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?

The input schema has one parameter (limit) with 0% description coverage, and the tool description doesn't mention any parameters. Since there's only one parameter and schema coverage is low, the baseline is 3, as the description doesn't add value beyond the schema but also doesn't mislead.

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 'Show recent activity feed' states the tool's purpose with a verb ('Show') and resource ('recent activity feed'), but it's vague about what 'activity' entails and doesn't distinguish it from sibling tools like list_cards or list_conversations. It provides a basic function but lacks specificity.

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 is provided on when to use this tool versus alternatives. With many sibling tools for listing items (e.g., list_cards, list_conversations), the description doesn't clarify the context or exclusions for selecting this tool, leaving usage ambiguous.

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