update-fleet-schedule

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

No annotations are provided, so the description must disclose behavioral details. While 'Update' implies mutation, it doesn't specify whether it's a partial update, what permissions are needed, error cases, or side effects. The description is too brief for a mutation tool.

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 a single sentence that is front-loaded with the verb and resource, listing the key fields. It is concise without any fluff, earning its place.

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?

Given 6 parameters including a nested object, no output schema, and no annotations, the description is insufficient. It does not explain the recurrence rule structure, whether other fields are ignored or preserved, or any constraints. The tool is a simple list of fields without essential context.

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 parameters are described in the schema. The description adds a summary of updatable fields, but no additional semantics beyond what's in the schema. This meets the baseline requirement.

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 clearly states the action 'Update' and the resource 'fleet schedule', listing the specific fields (name, query, recurrence rule, status) that can be updated. This distinguishes it from related tools like create-fleet-schedule or delete-fleet-schedule.

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 does not provide any guidance on when to use this tool versus alternatives, such as create-fleet-schedule for new schedules or get-fleet-schedule for reading. It also fails to mention prerequisites like requiring the schedule ID or that updates are partial.

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