get_flow_session

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no note on what a session contains, whether ids are tenant-scoped, or what happens with an unknown id. With annotations doing all the work, this is a minimal contribution.

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 fragments, front-loaded with the action and no filler. The second sentence is nearly redundant with the first, but the size is well matched to the tool's simplicity.

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 tool with no output schema, the description carries the burden of explaining what is returned, and it says nothing about the session object's contents, shape, or error behavior. Combined with zero usage guidance among many flow-related siblings, an agent has to guess at both selection and interpretation.

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?

With a single parameter at 100% schema description coverage, the schema already documents the id. "By id" in the description merely echoes the schema's "Numeric id." and adds no format, provenance, or lookup semantics, so the baseline of 3 applies.

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?

"Get a flow session. One session by id." names a verb and resource, but it largely restates the tool name and title. The phrase "one session by id" adds a hint of singular retrieval, distinguishing it weakly from list_flow_sessions, yet the sibling is never named and the distinction is left implicit.

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 use this instead of list_flow_sessions, list_flow_session_events, or get_flow. The agent must infer that this is the single-record lookup from the word "one" alone, with no prerequisites or exclusions stated.

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