Builder Console flows & deep links

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

Annotations already mark this as readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description's addition of return content (deep links, platform-cli equivalents) and filtering behavior adds practical context. The description aligns with annotations and goes beyond them by specifying what data is returned.

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 concise, starting with the core action and list of flows, then adding the parameter tip. It's front-loaded and every sentence adds value. A slightly more structured format could separate the flow list from the parameter note, but overall it's efficient.

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 simple listing tool with one optional parameter, the description covers the main usage: listing flows and filtering. It also mentions platform-cli equivalents, which helps in scriptable contexts. It doesn't describe the return structure explicitly, but given no output schema and simplicity, it's reasonably complete.

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?

The input schema has 0% description coverage on the `flow` parameter, but the description explicitly explains 'Pass `flow` for one entry,' giving the parameter purpose. It doesn't enumerate valid values but the flow names are listed earlier, providing indirect meaning. This compensates adequately for a single optional parameter.

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 clearly states the tool lists Builder Console flows with deep links, enumerating specific flow names. It's specific about the resource (Builder Console) and the action (list), and differentiates from sibling tools by focusing on console flows and platform-cli equivalents, which none of the other tools do.

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?

The description mentions passing `flow` to get a single entry, providing some usage guidance. However, it does not contrast with alternatives like avax_plan_l1_launch or avax_icm_recipe, nor does it state when to prefer this tool over others. The usage context is implied (for listing console flows) but lacks explicit exclusions or comparisons.

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