jobber_get_schedule

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

The description adds useful behavioral detail beyond the schema: the default range is today, period strings are convenience selectors, and explicit dates are an alternative. However, with no annotations, it leaves gaps such as timezone handling, whether startAt/endAt must be supplied together, pagination, and return shape.

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?

Two sentences with the primary action front-loaded. It covers the default, the named period options, and the explicit-date alternative without filler or redundancy.

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 getter with 3 optional parameters and no output schema, the description provides the core invocation knowledge: what the tool returns conceptually, the default behavior, and the two filtering modes. It leaves a few edge-case clarifications unstated, but nothing that would prevent correct basic use.

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?

The schema already documents all three parameters, so the baseline is 3. The description restates the period values and the default and positions startAt/endAt as a custom range, but adds little beyond the schema's own descriptions.

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 the specific operation ('Get the schedule'), the resource ('upcoming visits/appointments'), and the source system ('from Jobber'). The note about defaulting to today and the period options further define scope, and no sibling tool covers schedule retrieval.

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?

Provides concrete selection guidance: use one of the named period values or supply explicit startAt/endAt dates, with today as the default. It does not explicitly name alternative sibling tools or exclusions, but the schedule resource is unique among the siblings, so the context is sufficient.

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