katto_list_scheduled_posts

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so repeating 'Read-only' adds nothing; but the description goes well beyond them by disclosing the exact response object fields, the status lifecycle semantics, and the pagination contract. It does not mention rate limits or auth scoping, keeping it from a 5.

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?

Front-loaded scope, then response shape, then status semantics, then pagination — every clause carries information and none is redundant padding despite the density.

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?

With no output schema, the description supplies the return shape, field list, status meanings, and pagination mechanism, which is everything an agent needs to call and interpret results 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?

Schema coverage is 100%, so the structured fields already document limit, cursor, and status, giving a 3 baseline. The description adds modest value by restating cursor as 'the previous next_cursor' and elaborating the status values in lifecycle terms ('posting = being published, failed = see error'), slightly beyond the schema's terse enum 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 a specific verb+resource ('list ... scheduled social posts') and even names the origin of the data (katto_publish_clip with schedule_at, or the dashboard calendar), which distinguishes it from katto_list_jobs and katto_cancel_scheduled_post without opening any schema.

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?

Gives clear operational context: newest-first ordering, how to paginate via cursor, and the optional status filter. It does not explicitly say when to prefer this over katto_list_jobs or how it relates to katto_cancel_scheduled_post, so it stops short of naming alternatives/exclusions.

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