get_chimp_chatter

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by specifying that the tool returns a JSON with total_items and chimp_chatter array, and describes the structure of each entry. It does not contradict annotations.

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 concise, with every sentence adding value. It front-loads the purpose, provides usage guidance, lists args, and describes return format. No unnecessary 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?

Given the tool's simplicity, the description covers purpose, usage, parameters (mostly), and return format. The presence of an output schema in the description further aids completeness. However, the 'account' parameter is left unexplained.

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 0% description coverage. The description explains count (range 1-1000, default 10) and offset (pagination usage), but does not explain the 'account' parameter. This partially compensates for the missing schema descriptions.

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 'Retrieve the account activity feed (Chimp Chatter) of recent events across the account.' It uses a specific verb ('Retrieve') and resource ('account activity feed'), and distinguishes from sibling tool get_campaign_report by explicitly stating its use for metrics on a single campaign.

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 explicitly says when to use this tool: 'Use to review a chronological stream of account-wide activity'. It also provides a clear alternative: 'Use get_campaign_report for metrics on a single campaign instead.' This helps the agent decide between tools.

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