ztw_list_public_account_details

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

Annotations already declare readOnlyHint=true, aligning with the description's 'read-only' tag. The description adds no further behavioral traits (e.g., pagination, rate limits, data freshness). Given annotation coverage, this is adequate but not exceptional.

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, focused sentence with no wasted words. However, it is too terse and lacks structure (e.g., separate sections for purpose, usage, parameters). It could be expanded without becoming verbose.

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 omits essential context: no explanation of what 'public-cloud account details' include, no pagination semantics, no return value structure (no output schema). Given the absence of an output schema, the description should at least hint at the type of data returned, which it does not.

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?

With only 33% schema description coverage, the description fails to compensate by explaining parameters. It does not mention page, query, or page_size, despite the schema's detailed description for query alone. This is a significant gap for a tool with three 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 includes a specific verb ('List') and resource ('ZTW public-cloud account details'), clearly distinguishing it from sibling list tools that target other resources like IP groups or admins. However, it does not explicitly differentiate itself, leaving some ambiguity about the exact nature of '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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states what it does, leaving the agent without context for selection among many read-only list tools.

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