post_analytics_report

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context that the annotations cannot express: daily granularity, per-day confirmed/cancelled booking counts, per-day commission figures, currency inclusion, and aggregated period totals – which matters because there is no output schema.

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?

At roughly 200 words across five markdown sections, the description is bloated and self-repeating: 'What You Get' and 'Key Features' both re-list sales, bookings, commissions and revenue, and the Overview already said the same thing. The front-loading is good, but much of the content does not earn its place.

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?

With no output schema, the description carries the burden of describing results, and it does so credibly (daily sales, confirmed/cancelled counts, commissions, aggregated totals). What is missing for a reporting endpoint is whether the range is bounded, how timezone/currency selection works, and whether results can be large – but nothing essential to invoking it correctly is absent.

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 100% and both parameters (from, to) are documented in the schema with ISO 8601 YYYY-MM-DD format. The description only repeats 'Provide start and end dates', adding no syntax, range limits, or timezone guidance, so this is the baseline case where the schema does the work.

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 Overview states a specific verb and resource ('Get comprehensive analytics covering sales, bookings, commissions, and revenue for your date range') and the scope (daily granularity for a date range), which distinguishes it from most data-lookup siblings. However, it never names the closely overlapping analytics siblings (post_analytics_hotels, post_analytics_markets, post_analytics_weekly, post_commissions_report), so the agent must infer why this one is 'complete' rather than specialized.

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 'When to Use' section lists contexts (executive dashboards, financial reporting, booking analysis), but those bullets largely restate the output categories rather than telling the agent when this tool wins over a sibling report. There is no exclusion, no 'use X instead when Y', and with five or more overlapping reporting tools that is a real routing gap.

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