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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description contributes nothing beyond that — no indication of what the computation produces, whether venue/extras/catering are totals or per-unit amounts, or what currency/units apply.

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?

Three words is not conciseness here but under-specification; there is no front-loaded statement of purpose beyond the title. Every sentence would have earned its place, but there is essentially no substantive sentence to evaluate.

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?

A five-parameter computational tool with no output schema, no parameter descriptions, and no annotation-independent explanation is left entirely opaque. An agent cannot confidently invoke it correctly — the description is far too thin for the complexity.

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% across all 5 parameters (venue, extras, guests, catering, costPerGuest), and the description supplies no parameter meaning at all. For a budget calculator where the distinction between a total and a per-item or per-guest amount completely changes the result, this is a critical omission.

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 'Event budget planner' essentially restates the tool name (planning_event_budget) without a specific verb or explanation of what it computes or returns. An agent learns only the domain, not the operation — it cannot tell whether this returns an estimated cost, a breakdown, or an allocation from this text.

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, no prerequisites, and no routing to alternatives among the ~40 siblings (e.g. planning_monthly_budget, planning_split_bill, planning_cost_of_living). The agent must infer the use case entirely from the name.

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