conduyt_list_report_schedules

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

With no annotations provided, the description does carry the full burden, and it does useful work by disclosing the shape of what comes back: cadence, time, formats, recipients, next and last run. It says nothing about it being a read-only operation, permission requirements, or whether all schedules are returned unpaginated.

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?

A single sentence that front-loads the resource and uses the parenthetical to enumerate the returned fields efficiently. Nothing is wasted and nothing is buried.

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 one-parameter read tool with no output schema, listing the returned fields compensates well for the missing output schema. The remaining gap is that nothing routes the agent away from the similarly named report_schedule_deliveries or the schedule CRUD siblings.

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?

Only one parameter exists and the schema documents it fully ("Saved report id", uuid format), so the schema already carries the semantics. The description's phrase "on a saved report" loosely reaffirms the scope but adds no format or scoping detail beyond the schema.

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 names a precise resource: the scheduled deliveries attached to one saved report, with the delivery channel (email) and formats spelled out. It never states the verb (list/retrieve) and does not distinguish itself from the sibling conduyt_report_schedule_deliveries, which an agent could easily confuse it with.

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?

There is no guidance on when to call this versus conduyt_list_reports, conduyt_report_schedule_deliveries, or conduyt_send_report_schedule_now. The usage condition (inspecting schedules for a known report id) is only inferable from the noun phrase.

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