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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing the null case ("null if none was ever set"), which tells the agent how to detect an unscheduled flow. It says nothing about behavior for an unknown versionId/workspaceId, permission requirements, or error handling.

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 return value and the field source, with the null case stated immediately after. Nothing superfluous.

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 two-parameter read tool, the description covers the essential unknown — what it returns and what it returns when nothing is set — which matters since there is no output schema. The remaining gap, ID provenance, is minor against the tool's simplicity.

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 description coverage is 0%, so both required strings are undocumented in the schema. The description gives no meaning for versionId or workspaceId — not their format, where version IDs come from, or whether workspaceId scopes the lookup — so it fails to compensate for the coverage gap.

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 and resource ("Return the flow version's current schedule") and even names the underlying field, metaInfo.schedule. It does not explicitly name the sibling set_flow_schedule, but the read framing makes the read-vs-write split with that sibling inferable.

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 only implied by the word "Return"; there is no explicit when-to-use or when-not-to-use guidance. An agent can reasonably infer this is the read counterpart to set_flow_schedule, but it has to draw that inference itself.

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