listar_modelos

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

With no annotations, the description carries the behavioral disclosure burden. It usefully explains that matching is case-insensitive, that the filter applies to the path, and that unfiltered results are numerous. This goes beyond the schema, though the interaction with the 'limite' parameter is not fully clarified.

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 compact and front-loaded: one sentence establishes purpose, and the next gives filter semantics and a practical warning. Every sentence contributes useful information with no filler.

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 output schema covers return values, so that is not a gap. The core listing behavior and filter are well described, but the 'limite' parameter is undocumented and its default appears inconsistent with the 'hundreds' claim, leaving a material gap for an agent trying to control result size.

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 0%, so the description must compensate for both parameters. It explains 'filtro' well with examples and case-insensitivity, but 'limite' is never mentioned or described. Additionally, saying unfiltered results are 'hundreds' sits awkwardly with the schema default of 40 for 'limite', leaving result-size behavior unclear.

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 a specific action and resource: it lists .ttm models from the CoppeliaSim-installed library. This distinguishes it from sibling tools like listar_objetos, which presumably operate on the current scene rather than the model library.

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 explicit practical guidance: use a filter to narrow results by path substring and avoid overly large result sets without one. It does not explicitly contrast with alternatives such as listar_objetos, but the context of use is clear and no misleading exclusions are present.

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