Reports_cancelReportSchedule

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

With no annotations, the description must disclose side effects, required context, and operational behavior, but it only says the schedule is cancelled. The phrases 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are ambiguous and do not clarify whether cancellation is destructive, reversible, or requires special permissions.

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 definition is short, but 'Catalog entry' is filler and 'Runs in your Kuudo deployment, not here' is vague context that is not clearly actionable. The core action appears only in the final sentence, so the content is not well front-loaded.

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 cancellation tool with no annotations and no output schema, the description should explain what identifier to pass, what a successful cancellation returns, and what effects it has. None of that is present, so an agent does not have enough information to invoke the tool 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?

The schema defines zero properties, so the description's 'that you specify' is the only hint that a schedule identifier must be supplied. It does not name the expected parameter or its format, and with additionalProperties set to true the agent is left unsure what input to provide.

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 phrase 'Cancels the report schedule that you specify' identifies a specific verb and resource, so an agent can see this acts on report schedules rather than on reports or shipments. However, the opening 'Catalog entry' and 'Runs in your Kuudo deployment, not here' add confusion, and the description does not explicitly distinguish it from sibling tools like Reports_cancelReport.

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?

No guidance is given about when to choose this tool over alternatives such as Reports_getReportSchedule, Reports_getReportSchedules, or Reports_cancelReport. The only contextual clue, 'Runs in your Kuudo deployment, not here', speaks to execution location rather than usage conditions.

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