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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context of its own — nothing about pagination, ordering, result size, or what a page of results contains.

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?

It is a single short clause with no filler, so nothing is wasted, but it is under-specified rather than concise — the brevity comes at the cost of stating an action or any usage context. There is no front-loaded statement of what the tool returns.

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?

This is a simple, parameterless-required list tool with a fully documented schema and rich read-only annotations, so the bar for the description is low. Still, an agent gets no statement that this returns a paginated collection of flow schemes, and a brief pointer to get_flow_scheme for single-record retrieval would close the remaining gap.

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 100%: page, search and per_page are each documented, including defaults and the 1-100 bounds on per_page. The description contributes nothing beyond the schema, 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?

The description is a noun fragment, 'Flow schemes (reusable routing trees)', that names the resource and adds a useful gloss defining what a flow scheme is. It never states the action (listing/retrieving a collection), and it does nothing to separate this tool from the many siblings over the same resource (get_flow_scheme, create_flow_scheme, update_flow_scheme, apply_flow_scheme).

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 when-to-use guidance at all: no indication of when to call list_flow_schemes versus get_flow_scheme for a single record, or when pagination/search should be used. The only mild signal comes from the tool name itself, not the description.

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