get_week

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no indication that this is a read-only operation, no auth or rate-limit context, no statement about whether closures or cancellations appear in the week, and no timezone or week-boundary behavior. The single clause about grouping by day is the only behavioral fact offered.

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?

One short sentence, front-loaded, with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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?

Placeholder.

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 67%: week_of and program_type are documented well in the schema, but include_description has no description anywhere. The description adds zero parameter meaning beyond the schema and does not compensate for the undocumented flag, so it falls below the baseline expected at moderate coverage.

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 names the resource and scope ('A Monday-Sunday week of programs, grouped by day'), which tells an agent what comes back, but there is no verb and no differentiation from siblings like get_events_range or get_events, which plausibly overlap. An agent cannot tell from the description alone why it should pick this over a date-range call.

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 when-to-use guidance at all: no mention of when this is preferable to get_events, get_events_range, or search_events, and no exclusions. The only routing hint in the whole definition lives in the schema's program_type description pointing at list_program_types.

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