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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds real behavioral context: automatic derivation of the previous period of equal length, ordering by current-period sales, limit-bounded output, and the null previous_period for new hotels. Does not mention rate limits or pagination beyond 'limit'.

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?

Markdown headers (Overview, When to Use, What You Get, Quick Start) front-load purpose and usage. Content is a bit long with some overlap between Overview and Quick Start, but every section earns its place for an analytics endpoint. Slight redundancy keeps it from a 5.

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?

No output schema exists, yet the 'What You Get' section documents the return shape in detail (period metadata, summary totals, per-hotel fields, nulls for new properties). This compensates well for the missing output schema. It still omits guidance on limits, defaults, or authentication, so it's complete but not exhaustive.

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%, so baseline is 3. The description goes beyond the schema by explaining that the previous period is auto-derived from from/to and that limit ranks by current-period sales, adding semantic value about how from/to and limit interact with the result set.

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?

States a specific verb+resource: returns hotel-level sales analytics (sales, buying price, profit, margin) with period-over-period comparison. Scope is concrete and concrete metrics are named. However, it never contrasts itself against closely related siblings like post_analytics_hotels or getPriceIndexHotels, so an agent can't tell from the description alone which of these to call.

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' block gives implied usage (property performance, period comparison, profit analysis, dashboards) but does not name alternatives or exclusion conditions, e.g., when to prefer post_analytics_report or post_analytics_markets. Useful but not decisive for sibling selection.

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