gazebo_models

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

With no annotations provided, the description carries full responsibility for disclosing behavioral context. It mentions an external source (fuel.gazebosim.org) and simulation integration, but does not disclose side effects such as downloading files, deleting local models, network dependence, or requirements for a running Gazebo environment. This is a significant gap for a tool that includes deletion and download operations.

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 short and front-loaded, but the first sentence's verb list 'browse, download, and spawn' is repeated in the second sentence without much new information. The second sentence adds useful context about the source and model count, but the redundancy keeps it from being fully polished.

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?

The tool is moderately complex with 11 parameters and 5 enum operations, yet the description covers only 3 of the 5 operations and omits 'list_local' and 'delete_local'. It also does not explain behavioral implications of spawning into a simulation or managing local model storage, so an agent could miss important side effects despite having the full schema available.

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 description coverage is 100%, so the schema already documents all 11 parameters, including x/y/z spawn positions, pagination, search filters, and operation names. The description adds only high-level context about spawning into Gazebo and does not meaningfully extend or clarify the parameters 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?

The description names a specific resource (Gazebo Fuel simulation models) and concrete actions (browse, download, spawn), which makes the tool's general purpose clear. However, it omits 'list_local' and 'delete_local' operations and does not explicitly differentiate itself from sibling tools like sim_marketplace_search_tool.

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 implies usage: use this tool when working with Gazebo Fuel models and bringing them into a Gazebo simulation environment. It provides no explicit guidance on when to choose this tool over alternatives or when to avoid it, nor does it explain when each operation should be used.

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