ztw_list_public_account_details

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

The description claims 'read-only', which merely echoes the annotation readOnlyHint:true and adds no new behavioral information. No rate limits, pagination details, or field naming quirks are mentioned beyond what's already in structured data.

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?

One short sentence with zero filler words. Every word carries meaning, and it is perfectly front-loaded with the core action and resource.

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?

Without an output schema and with only terse descriptions, the tool lacks essential context like default page size, result limit, or any explanation of what 'public-cloud account details' entails. Compared to sibling tools that may have more informative descriptions, this is incomplete.

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 tool description says nothing about parameters. The schema has a rich description for 'query' but 'page' and 'page_size' have no descriptions, and with schema description coverage at only 33%, the description does not compensate for the undocumented parameters.

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 'List ZTW public-cloud account details (read-only)' uses a specific verb and resource, clearly stating what the tool does. However, it does not explicitly distinguish it from the very similar sibling tool 'ztw_list_public_cloud_info', so no sibling differentiation is provided.

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 provides no guidance on when to use this tool versus its many alternatives. There is no mention of use cases, prerequisites, or references to other list tools, leaving the agent without any usage direction.

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