iaas_get_fabric_computes

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that profile — no pagination defaults, no note about result volume or ordering — it merely restates the operation and echoes the HTTP path.

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?

It is short, but not efficient: line two ("Get all fabric computes") is a near-verbatim restatement of line one, and line three is just the HTTP route already reflected in the title annotation. Two of three lines do not earn their place.

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 simple read-only list with full schema coverage and rich annotations, the description is minimally sufficient to call correctly. What it lacks is disambiguation from the ~350 siblings — especially iaas_get_fabric_compute (single) and iaas_get_computes — which is the one piece of context an agent here actually needs.

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%: top, skip, count, filter and apiVersion are each documented in the schema, including filter operators and the count flag's behavior. The description adds no parameter meaning beyond the endpoint path, so the baseline 3 applies.

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?

States a specific verb and resource ("Get all fabric computes"), so the agent knows this is a collection read of fabric computes. However, it does nothing to distinguish itself from the singular sibling iaas_get_fabric_compute or from the adjacent iaas_get_computes resource, leaving discrimination to the name alone.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., a cloud account or integration must exist), and no reference to the singular or non-fabric compute siblings. The agent must infer usage entirely from the tool name.

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