Transforms, Machines y proveedores

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by explaining that the inventory includes integrated transforms without API keys, provider transforms with API keys, and TRX/iTDS servers, and that check_servers=true performs a connection check.

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 a single front-loaded sentence that begins with 'Inventario' and packs the key scope, filters, and check_servers behavior without obvious filler. It is dense but appropriately sized for a list tool.

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 read-only inventory tool with no output schema, the description covers the main content returned (transforms, Machines, provider/server status) and the optional connection check. It leaves return formatting details to the schema, which is acceptable given full parameter coverage.

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 all five parameters are already documented in the schema. The description reinforces category/entity_type filtering and check_servers behavior but does not add meaning beyond the schema for response_format or include_machines.

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 it is an inventory of transforms, Machines, and provider/server status, with filtering by input type or category. It implicitly distinguishes itself from run-oriented siblings like osint_run_transform and osint_run_machine by focusing on listing available resources rather than executing them.

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?

It explains that results can be filtered by input type or category and that check_servers=true verifies connections, which implies when to use the tool. However, it does not explicitly say when to choose this over osint_run_transform, osint_run_machine, or osint_list_entity_types, nor does it state exclusions.

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