ztna_cloud_integration

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

readOnlyHint=true already declares this is a safe read, so the "[READ]" prefix in the description adds nothing new. The description says nothing about behavior when integration_id is unknown, whether errors or empty results are returned, or what fields come back — and with no annotations covering those, the burden was on the description.

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 single sentence is front-loaded and free of waste, but brevity here crosses into under-specification rather than disciplined concision. A few more words on ID source and return shape would have earned 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 one-parameter lookup with no output schema, an agent still needs to know how to obtain a valid integration_id and roughly what the response contains. Neither is covered, and there is no output schema to fall back on, so the definition is incomplete for its purpose.

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% for the single required parameter, so the description should explain what integration_id is (ID format, where to obtain it, e.g. from ztna_cloud_integrations). It provides none of that, leaving the parameter completely undocumented in both structured and prose form.

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?

"Read one cloud integration" gives a verb (Read) and resource (cloud integration), and the word "one" hints at the singular counterpart to the plural ztna_cloud_integrations sibling. However, it never names that sibling or states scope, so the agent must infer the list-vs-single distinction from naming conventions 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 guidance on when to use this tool versus ztna_cloud_integrations, nor any prerequisite or exclusion. The only usable signal is that it retrieves a single object, which the agent must derive from the word "one."

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