ztw_list_public_cloud_info

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

The description correctly states the tool is read-only, aligning with the readOnlyHint annotation. It adds the JMESPath client-side filtering feature, which is useful. No contradictions and no additional behavioral details needed beyond annotations.

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?

Two concise sentences that front-load the purpose and add a key feature. No wasted words, efficient 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 is adequate for a simple list tool with a good schema and output schema, but it lacks context about when to use this over siblings and does not mention pagination or other operational details. It is minimally complete.

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% and already explains each parameter well. The description only repeats the JMESPath aspect from the query parameter schema, so it adds no new meaning beyond the schema.

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 verb 'List' and the resource 'ZTW public cloud accounts with metadata', and mentions read-only and JMESPath filtering. However, it does not explicitly differentiate from similar sibling tools like 'ztw_list_public_account_details'.

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 on when to use this tool versus alternatives, no exclusions or prerequisites mentioned. The only usage hint is the JMESPath filtering capability.

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