Sessions of a week

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds the meaningful negative constraint that it does not count enrollments, plus 'one row per session' cardinality. The column list partly duplicates the existing output schema, so it is useful framing rather than new disclosure.

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?

Front-loads scope, window, and row shape in one sentence, then adds a short usage note and a single redirection. No filler, and the most load-bearing constraint (the date window) comes first.

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?

With an output schema present, the description needn't explain return values, and both parameters are documented at 100% coverage. The remaining gap is ordering/limits (whether results are sorted or capped), which an agent might want but is not essential to invoke 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, but the description adds real meaning: the week is inclusive from the given Monday through the next Sunday, which the schema's 'Monday of the week' phrasing never states. The status filter is left to the schema, where its enum and default are already documented.

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 training sessions), pins the exact window (monday through the next Sunday), and names the row granularity and returned columns. It also distinguishes itself from session_detail, so an agent can separate the two without opening either schema.

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?

'Use it to find sessions by date' gives positive context, and 'for one session whose id you know, call session_detail' names an explicit alternative with the condition that selects it. It does not cover other plausible routes (e.g. watchlists or cancellation-related lookups), but the core use/alternative pair is clear.

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