followup_get

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

With no annotations, the description warns that action_items are raw portal data and need transcript for ownership resolution, and notes transcript is heavy. This adds valuable behavioral context, though no side effects or permissions are mentioned.

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 two sentences with a warning, front-loaded with purpose. Every sentence adds value and is efficiently presented.

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 complexity (call breakdown with action items) and presence of output schema, the description covers key behavioral aspects. Could mention participants more explicitly, but sufficient.

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 coverage is 50% (only transcript described). The description adds meaning by explaining how to use transcript to resolve task ownership, which goes beyond schema, compensating for missing call_id description.

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 the tool returns call breakdown: topic, agenda, agreements, action items, participants. This is specific and distinct from sibling followups_list which likely lists all followups.

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 guidance on when to set transcript=True for interpreting action items, but does not explicitly state when to use this tool vs alternatives or exclude cases. Adequate but not explicit.

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