create_report

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'Generate... reports' which implies a read-only operation, but doesn't disclose authentication needs (though 'meta_access_token' parameter hints at this), rate limits, whether it's synchronous/asynchronous, or what the output contains beyond 'reports'. More context on the tool's behavior is needed.

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 that gets straight to the point without unnecessary words. It's appropriately sized for a tool name like 'create_report', though it could be more informative given the complexity.

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 (12 parameters, no annotations, 0% schema coverage) and the presence of an output schema, the description is inadequate. It doesn't explain parameter usage, behavioral traits, or how it differs from siblings. While the output schema might cover return values, the description lacks essential context for proper tool selection and invocation.

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 0%, so the description must compensate but fails to do so. It doesn't explain any of the 12 parameters, such as what 'OSS-local' means, valid values for 'report_type' or 'export_format', or how 'date_range' should be formatted. The description adds no parameter semantics beyond what's inferred from parameter names.

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 action ('Generate') and resource ('OSS-local performance reports for Meta Ads accounts/campaigns'), making the purpose understandable. However, it doesn't explicitly differentiate this reporting tool from other reporting-related tools like 'list_insights' or 'search_ads_archive', which might offer similar data in different formats.

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. The description doesn't mention prerequisites, such as needing a Meta Ads account, or compare it to other tools that might retrieve similar data (e.g., 'list_insights' for raw data vs. this for formatted reports).

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