get_r_asset_asset_ports

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

No annotations are provided, so the description carries the behavioral burden. It transparently signals a read-only operation via 'Retrieve' and 'GET /r/asset/asset_ports', and clarifies parameter placement. However, it does not disclose authentication requirements, route ID semantics, or other behavioral details beyond the obvious GET semantics.

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: the core operation appears in the first sentence, and the second sentence efficiently conveys parameter routing. The explicit 'Calls GET /r/asset/asset_ports' is slightly redundant after 'Retrieve asset ports' but not wasteful.

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 description covers the main request-construction steps and an output schema exists for return values, but it leaves gaps: what 'route IDs' refers to, whether body should ever be used, and how this endpoint differs from the closely named get_r_asset_asset_ports_id are all unspecified. It is adequate for a generic REST wrapper but not complete for confident selection among many similar tools.

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% and all four parameters are generic empty containers, so the description's mapping of path_params, query, and headers to specific content types is genuinely valuable. It tells the agent where route IDs, filters/pagination, and headers belong, though it does not enumerate possible query filter keys or address the 'body' parameter.

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 opens with 'Retrieve asset ports,' a clear verb+resource statement that identifies the operation. It also names the exact endpoint, though it does not explicitly differentiate itself from similar siblings like get_r_asset_asset_ports_id.

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 parameter-placement instructions ('Provide route IDs in path_params, filters and pagination in query...') but offers no guidance on when to use this tool versus alternatives. With dozens of asset-related siblings, the absence of any when-to-use or when-not-to-use context leaves selection to the agent's inference.

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