Get a schedule group by id

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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context about the response shape varying by kind: TimeInterval returns start/end times, while RecurringGroup returns weekly windows under 'schedules'. This goes beyond simple getter behavior, though it omits error handling or side-effect notes.

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?

The description is two sentences: the first states the core purpose, the second adds necessary detail about shape variance. No wasted words, front-loaded with the primary action.

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 simple get-by-id tool with one parameter and an output schema, the description is sufficiently complete. It supplements the schema by explaining how the response varies by group kind. It could mention what happens if the ID does not exist, but that is not essential for a getter.

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 0%, but the single parameter group_id is self-explanatory from the name and title. The description does not elaborate on the parameter format or constraints, but the meaning is unambiguous. This is adequate compensation for a trivial parameter.

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 begins with 'Fetch one schedule group,' which clearly states the action (fetch) and resource (schedule group). It indicates this is a single-item getter, distinguishing it from the sibling 'list_schedule_groups' tool. The title reinforces the 'by id' scope.

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 description clearly implies use for retrieving a single schedule group by ID, and the sibling list includes list_schedule_groups for bulk retrieval. However, there is no explicit statement of when to use this tool over alternatives or exclusions, so it stops short of a 5.

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