ztw_list_public_cloud_info

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

The description includes 'read-only', consistent with the readOnlyHint annotation. However, it does not add any additional behavioral context such as pagination, rate limits, or side effects beyond what is already implied by the annotation. Since the annotation already covers the main read-only aspect, the description adds minimal value.

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, concise sentence that clearly states the tool's purpose without unnecessary verbiage. It is well-structured and easy to parse.

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 provides the essential purpose and read-only nature, but lacks broader context such as typical use cases, relationship to other tools, or any note on return structure. Given the simple list operation and no output schema, it is adequate but not comprehensive.

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?

The description fails to explain any of the five parameters (page, query, search, page_size, cloud_type). Only the 'query' parameter has a description in the schema, leaving the others unexplained. With low schema coverage (20%), the description was expected to compensate but does not, making parameter semantics entirely opaque.

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 the action 'List' and the resource 'public-cloud account info', making the purpose unambiguous. It also adds '(read-only)' to confirm it is a non-mutating operation. This is distinct from other list tools by specifying the ZTW public-cloud scope.

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?

No guidance is provided on when to use this tool versus alternatives, such as the similarly named 'ztw_list_public_account_details'. There is no mention of use cases, prerequisites, or exclusion criteria, leaving the agent to guess when this tool is appropriate.

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