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

Annotations carry only a title, so the description bears the full burden and delivers: the config env var and default endpoint, the hub-side kind=agx-flow filter plus client-side re-filtering so clones never surface, and the explicit failure mode for hubs predating the kind protocol. Return fields (name/description/version/downloads) are also disclosed.

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?

Front-loaded with the core action and the flow_install handoff, then the implementation caveats. Dense but every clause (env config, clone filtering, unsupported-kind error) carries real information; the kind-protocol sentence is slightly verbose but earns its place.

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?

No output schema exists, but the description names the returned entry fields and covers the notable edge case, so an agent has enough to call and interpret it. Minor gaps remain (pagination, whether an empty hub vs empty query differ) but nothing blocking.

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 coverage is 100% and the single query param is fully documented there, so baseline is 3. The description's kind-filter detail is hub behavior rather than added meaning for the query argument itself, which the schema already describes as a name/description substring.

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+resource (list flow packages installable from the hub) and explicitly positions itself against the sibling flow_install by framing the task as flow discovery. An agent can tell this is lookup/discovery rather than installation without opening another schema.

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?

Explicitly routes the agent: 'flow_install takes a name, this is how you learn the names', and gives the naming handoff ('feed the name to flow_install'). The when-to-use relationship to the sibling is unambiguous.

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