get_team_performance

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic operation (get aggregated data) but omits details like whether it's read-only, auth requirements, or rate limits. The 'Get' prefix suggests a non-destructive operation, but no explicit confirmation.

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 sentence with no unnecessary words. Every part is essential: the verb, resource, scope (across all campaigns for a team), and optional date range. Highly efficient.

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 tool retrieves performance data but has no output schema. The description does not explain what metrics are returned, how the data is structured, or any aggregation details. This leaves the agent guessing about the return format.

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 only 33% (team_id has description). The description adds context for date_from and date_to by saying 'within an optional date range', which compensates for the lack of schema descriptions for those parameters.

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 uses a specific verb 'Get' and clearly identifies the resource as 'aggregated performance data across all campaigns for a team', distinguishing it from sibling tools like 'get_campaign_performance' which is per 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 implies this tool is for team-level performance data across campaigns, and optional date range is mentioned. However, it doesn't explicitly state when to use this versus alternatives like 'get_campaign_performance' or provide exclusions.

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