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

Annotations already cover read-only, idempotent, non-destructive, and closed-world traits, so the bar is lower. The description adds real value beyond them: the exact return object shape and the auth-conditional rule that bookings/deals appear only if the caller may read those resources, plus the fact that bookings inline their contact.

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?

Extremely dense and front-loaded: purpose first, then return shape, then permission and nesting caveats. No sentence is wasted.

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, and the description compensates by enumerating the returned fields; it also flags the permission-dependent inclusion of bookings/deals and the inlined contact. An agent has everything needed to call and interpret it correctly.

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 the baseline is 3. The description adds genuine meaning the schema does not: the half-open interval notation [from, to) clarifies that 'from' is inclusive and 'to' is exclusive, which affects how the window is queried.

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 and resource set: a period report covering contacts, bookings, and deals created in [from, to), with the 'one-call' framing distinguishing it from the list_contacts/list_bookings/list_deals siblings. It does not name those siblings explicitly, so it stops short of a full 5.

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 'one-call period report' phrasing implies this replaces multiple list calls, but there is no explicit when-to-use/when-not statement against list_contacts, list_bookings, or list_deals. Usage must be inferred from the scope description.

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