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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description still adds two non-schema facts: the call is free (no credit cost), and the returned sheet/prompt content is customer data that must not be treated as instructions. It says nothing about ordering or pagination, but with zero parameters and a read-only annotation, this is above the bar.

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 short sentences with the substantive content front-loaded: what is returned, then cost, then the data-handling caution. The sentence fragment 'Free.' is abrupt but economical and carries real signal. No filler sentences to cut.

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 must convey the return shape, and it captures the main fields (Flow, sheet, tab, cadence, next run). It does not say whether records include identifiers needed by delete_schedule or cancel_flow_run, nor whether paused schedules appear. That is a meaningful gap for an agent that will chain this into schedule management.

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 tool takes no parameters, so there is no parameter semantics to explain and the baseline is 4. The description instead spends its words on the result shape, which is the right use of space for a zero-arg tool.

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 the resource (workspace schedules) and specifies the returned facts: which Flow runs on which sheet and tab, the frequency, and the next run time. That is concrete enough to distinguish it from sibling listing tools like list_flows, list_sheets, and list_prompts. It never uses an explicit verb like 'list' or 'retrieve', relying on the title to carry that framing.

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 statement of when to call this versus the adjacent tools (create_schedule, delete_schedule, get_flow, list_flows). The 'Free' note hints at a cost consideration that relates it to estimate_cost, but that is inference rather than guidance. An agent must guess the intended context from the tool name alone.

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