sim_fleet_status

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

With no annotations, the description carries the full behavioral disclosure burden. It indicates that the tool is a read-only probe that returns health data, strengths, and ports. However, it does not disclose possible side effects such as network calls to external processes, timeout behavior, or what happens when a backend is unregistered or unreachable.

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 succinct and well-structured: a single front-loaded summary sentence followed by the list of probed backends and the output. Every sentence adds value, and no unnecessary detail is present.

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?

This is a zero-parameter, read-only status probe. An output schema exists, and the description states what is acted on and what is returned (health data, strengths, ports). Nothing essential is missing for an agent to invoke the tool 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 tool has zero parameters, and the input schema reflects this with an empty properties object. Baseline for no parameters is 4, and the description need not discuss inputs. It correctly implies the tool takes no user-specified arguments by design.

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 purpose: 'Probe all registered simulation MCP backends and report availability.' It names a concrete action, a resource, and the specific backends checked (mujoco-mcp, gazebo-mcp, isaac-mcp, limx-robotics-mcp). It is clear but does not differentiate from sibling tools like sim_fleet_backends, so it loses the fifth point.

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?

Usage context is implied: this tool should be used when you need to check the availability of simulation backends. However, the description provides no explicit guidance on when to prefer this tool over alternatives such as sim_fleet_backends or sim_fleet_route, and no exclusion or comparison is given.

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