get_content_performance_report

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

With no annotations, the description carries full responsibility for revealing behavior, but it only states the tool creates a 'comprehensive performance report'. It does not disclose whether the operation is read-only, how data is aggregated, whether it has performance implications, or what constitutes 'performance' — leaving critical behavioral context undisclosed.

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 superfluous words, making it highly concise. However, it lacks any structural breakdown or additional context; while every word earns its place, it is too sparse to be fully informative.

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 has no output schema and no annotations, the description must compensate, but it fails to specify the return format, the meaning of 'performance', or the effect of report_type and metrics. With 4 parameters and numerous sibling tools, this description is insufficient for an agent to confidently select and invoke the tool.

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 100% with each parameter (period, metrics, report_type, include_comparisons) having its own description, so the description adds no additional meaning. The baseline of 3 applies because the schema already provides adequate parameter semantics, though the description could have been used to explain how parameters combine or what 'metrics' should contain.

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 'Comprehensive performance report across all content' clearly indicates the tool provides a performance report for all content, which is a specific resource and scope. It does not explicitly differentiate from sibling analytics tools like get_enhanced_insights or get_engagement_trends, but the phrase 'across all content' implies a broad aggregation unlike thread-specific tools.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any preferred scenarios, prerequisites, or exclusion criteria, leaving the agent to guess based on the tool name alone.

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