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

The annotations already declare this a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds genuinely useful access-control context — 'Requires Finance access (Owner, Admin, Finance, or Manager role)' — which is exactly the kind of prerequisite annotations cannot express. It says nothing about caching, date-range defaults, or result size, leaving minor behavioral gaps.

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?

Purpose is front-loaded in the first sentence, followed by the metric catalogue, then the access requirement — a logical order with no filler. The metric list is long-ish and slightly run-on, but every clause conveys distinct information.

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?

For a three-parameter analytics tool with no output schema, the description sketches what each metric returns and states the required role, which is enough to call it correctly. It omits the default behavior when start_date/end_date are both absent, a meaningful gap for an analytics tool since the implicit time window affects every result.

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?

With 100% schema description coverage, the schema already documents all three parameters, so the baseline is 3. The description earns above baseline by explaining what each enum value actually computes ('blended revenue-per-hour', 'team billable efficiency'), which is semantic meaning the enum list alone does not convey.

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 opens with a specific verb and resource ('Aggregate financial analytics for the organization') and immediately explains that metric_type selects among four distinct roll-ups, which lets an agent understand exactly what the tool produces. It stops short of naming which sibling tools (get_billing_report, get_budget_health, get_resource_utilization) it displaces, so the sibling distinction is only implicit.

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?

It gives clear per-metric selection guidance — project_margin_ranking for ranking project margins best/worst, revenue_summary for org budget health plus reported hours — which is real 'when to use which variant' guidance. It does not cover exclusions, i.e. when to prefer get_billing_report or get_budget_health instead of choosing a metric here.

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