sim_fleet_backends

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

No annotations are provided, so the description carries the behavioral burden. 'List' and 'offline registry' indicate a read-only operation that does not affect live state, which is adequate for this tool. It does not detail edge behaviors such as empty results or update cadence, but nothing here misleads an agent.

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 entire description is one front-loaded, efficient sentence. The parenthetical 'offline registry' adds meaningful clarification in two words, with no filler or redundant phrasing.

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?

With zero parameters, a fully-covered empty schema, and an output schema present, the tool is simple enough for the description to be complete. It tells the agent exactly what is being listed and where the data comes from, and there is no missing context an agent would need to invoke it 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?

The input schema has zero parameters, so there is nothing to document. The description reinforces that the operation is unconditional by saying 'all' registered backends, removing any expectation of filters or inputs. This meets the baseline for a parameterless tool.

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 uses a specific verb ('List') and a clear resource ('all registered sim backends and their capabilities'). The parenthetical 'offline registry' adds useful context that distinguishes this from live fleet status or routing tools, though it does not explicitly differentiate from siblings like sim_fleet_status or sim_fleet_route.

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 gives clear context by labeling this an 'offline registry', implying it is the tool to use when the static catalog of backends and capabilities is needed. It does not explicitly state when not to use it or mention any alternative tools, but for a simple list-all tool the context is sufficient.

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