reactflow_list_apis

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

No annotations provided, so description carries full burden. It states a list operation with no side effects, but does not disclose behavior like pagination, rate limits, or completeness guarantees. For a simple listing, this is adequate but not exceptional.

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?

Single sentence, front-loaded with the action and resource, no redundant words. Efficient and easy to parse.

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?

Given no output schema and simple parameter set, the description covers the essentials. It could mention the output format implicitly, but for a listing tool the purpose is clear. Missing a note about the output being a list of API names/objects, but overall sufficient.

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% with a well-described enum parameter. The description adds value by naming the categories ('components, hooks, utilities, and types') that align with the enum values, providing semantic context beyond the schema.

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?

Description clearly states 'List all React Flow v12 APIs - components, hooks, utilities, and types'. Verb 'list' is specific to enumeration, resource is clearly defined, and categories distinguish from sibling tools like reactflow_get_api which retrieves a single API.

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?

No explicit guidance on when to use this tool vs alternatives. While context implies it's for an overview of available APIs, the description does not mention when to filter by kind or when to use reactflow_get_api (for details on one API) or reactflow_search_docs. Lacks when-not-to-use advice.

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