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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, but the description adds meaningful traits: no API key required, summaries only with no flow body, no-arg behavior returns top examples, and empty results instead of errors. These are useful behavioral disclosures beyond the structured annotations.

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?

The description is a dense but front-loaded paragraph that leads with the action and resource before covering return shape and edge cases. Every sentence contributes, though it could be slightly tighter by separating the return-field list from the main flow.

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?

There is no output schema, so the description compensates by enumerating the returned summary fields (id, title, summary, useWhen, tags, requiredModules, hasSchemaExample) and explaining that full bodies require get_flow_example. Combined with the read-only annotations, an agent has enough to call this correctly.

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%, so the schema already fully documents tags, limit, and query semantics. The description adds only the high-level no-argument behavior and the empty-list edge case, which is consistent with the baseline when the schema carries the parameter detail.

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 ("Search the library of reusable flow examples") and scopes it with the business cases it covers. It also distinguishes itself from get_flow_example by explaining that this tool returns summaries only and that an id is needed for the full example.

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?

Gives clear routing to the sibling get_flow_example for full bodies, and explains the no-argument browse behavior and the empty-list case for unmatched queries. It does not explicitly compare against other search tools like search_flows, so it is not a full when/when-not statement, but the primary alternative is named.

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