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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is carried. The description adds domain behavior not in structured data: Wavelength emails the owner when a flow is due, which tells the agent this read reflects an automation-driven reminder system. It stops short of describing response shape or failure modes.

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 compact sentences with the resource and scope front-loaded and no filler. The second sentence about email reminders is short and earns its place as domain context, though it could arguably be 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 usefully enumerates the returned fields (last confirmation, interval, due date, staleness), which is exactly what an agent needs. It does not cover error cases such as an unknown flow_id, keeping it short of complete.

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?

Single required flow_id, schema coverage 100%, so the schema already documents the parameter. The description reinforces the single-flow scope ('one flow') but adds no format, sourcing, or lookup guidance beyond that. Baseline 3 is correct.

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?

Specific verb (Read) + resource (check-in status of one flow), and it enumerates what the status contains: last confirmation, interval in days, due date, staleness. An agent can distinguish it from the sibling update_checkin purely on read-vs-write verb.

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?

Usage is implied by 'one flow' scoping and the read framing, but the description never states when to reach for this versus update_checkin, get_flow, or list_flows, nor any prerequisite (e.g., owner/org membership). Adequate but leaves routing to inference.

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