List Bookings

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

No annotations are provided, so the description carries the full burden. It adds genuinely useful domain context with the booking-method legend (1=per day, 2=percentage, 3=total hours), but says nothing about read-only safety, pagination behavior beyond the schema's page fields, or what a result record looks like.

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 short sentences, front-loaded with the resource and the filter dimensions. The trailing booking-method legend is somewhat orphaned since no parameter exposes it, costing a small amount of focus.

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 seven-parameter list tool with no output schema and no annotations, the description covers purpose and filters adequately but omits what the response contains, whether results are paginated by default, and any permission or scope constraints. Adequate but with clear gaps.

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 100%, so every parameter is already documented and the baseline is 3. The description restates the filter dimensions and adds the booking-method enum mapping, but note that 'booking method' is not actually a filterable parameter here, so that detail is contextual rather than parameter-level guidance.

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 ('List resource bookings/scheduling from Productive.io') and clarifies the dimension being retrieved ('who is booked and when'). It never differentiates itself from the closest sibling, productive_list_time_entries, which an agent could easily confuse with planned bookings.

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?

'Filter by person, project, or date range to see who is booked and when' implies the intended scenario but states no explicit when-to-use condition and names no alternative. The distinction between planned bookings and logged time entries is not drawn, leaving the agent to infer it.

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