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

Annotations already disclose that this is a non-read-only, non-destructive, non-idempotent, open-world write, so safety profile is covered. The description contributes one genuinely new fact — the report goes to an external safety team — but says nothing about effect on the booking, whether the report is visible to the reported user, or what happens after submission. Additional value is real but thin for a mutation with 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?

A single front-loaded sentence with no filler — the core purpose lands immediately. It is arguably too terse rather than too long, but on the conciseness axis it is efficient.

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 non-idempotent write with no output schema and two undocumented parameters, the description should explain the third enum value, the free-text description field, and at minimum whether reporting is repeatable or has side effects on the booking. None of that is present, so the agent must guess at key invocation details.

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 only 33%: bookingUid is documented, but 'description' has no explanation anywhere and the enum values carry no semantics. The description partially compensates by mapping 'as spam' and 'as someone the user does not know' to two of the three reason values, but leaves 'OTHER' and the free-text description parameter entirely unaddressed.

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 ('Report') plus resource ('a booking') with the destination ('Caly's safety team'), which is more than a restatement of the title. It is distinguishable from sibling mutation tools like cancel_booking or report_wrong_assignment, though it never explicitly contrasts with report_wrong_assignment, which the agent could confuse it for.

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 scenarios named (spam, someone the user does not know) imply when to use it, but there is no explicit when-not guidance, no mention of prerequisites, and no pointer to the closest alternative (report_wrong_assignment) or to list_bookings as the upstream step. The implied usage is adequate but leaves the agent to infer.

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