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

Annotations already declare readOnlyHint=true so safety is known. Beyond that, the description adds the GraphQL field name (timeblocks) but nothing about pagination behavior, filtering constraints, or what is returned. With annotations covering the read-only profile, the description should still disclose key behaviors for a paginated list tool but does not.

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 compact sentence stating the resource, scope, and meaning, with a short GraphQL mapping note. Every element is front-loaded and no filler is present.

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 read-only paginated list tool with no output schema and full schema coverage, the description covers the essentials but omits return-shape guidance, pagination behavior, and when/how to use the query filter beyond what the schema states. 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 coverage is 100%, so the schema already documents all four parameters including the query filter syntax and cursor semantics. The description adds only the GraphQL field name 'timeblocks' and does not deepen parameter meaning beyond what the schema says. Baseline 3 applies.

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 (List) and resource (blocked time / timeblocks), and clarifies the scope as staff calendars at one location, with examples of what timeblocks represent. It does not explicitly contrast with sibling boulevard_create_timeblock or boulevard_list_shifts, but the resource name is distinct and unambiguous.

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?

No when-to-use guidance, no prerequisites, and no mention of related tools like boulevard_create_timeblock for writing timeblocks. The description states what it does but gives no routing context for an agent choosing among the many list_* siblings.

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