zdx_list_locations

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

The description explicitly states 'Read-only', which aligns with the readOnlyHint annotation. It adds value by explaining the output is 'curated id/name rows' and that the id is used for scoping other tools, which is beyond the annotation. It also clarifies the 'since' parameter's unit and default, which is not in the schema. No contradiction with 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?

The description is extremely concise, with three short sentences that pack essential information: purpose, read-only nature, usage of id, and 'since' unit. Every sentence earns its place, and it's front-loaded with the primary purpose. No fluff or redundancy.

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?

Given the tool's simplicity (list operation, no output schema, 3 optional params), the description is fairly complete. It covers the key behavioral aspects (read-only, id usage, since unit) and the schema covers 'query' well. The only gap is the 'search' parameter, which is undocumented in both schema and description, but this is a minor omission for a list tool.

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 only 33% (only 'query' has a description). The description compensates by explaining 'since' is in hours with a default of 2h, which is not in the schema. However, it doesn't explain the 'search' parameter, which remains undocumented. The 'query' parameter has a detailed description in the schema, so the description adds value for 'since' but leaves 'search' ambiguous.

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 tool lists ZDX locations as curated id/name rows, which is a specific verb+resource combination. It distinguishes itself from sibling tools by specifying the ZDX product scope and the curated id/name output format, which is not evident from the name 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?

The description provides clear usage context: it's read-only, and the returned id should be used as a location_id scope filter on other ZDX tools. It also explains the 'since' parameter is in hours with a default of 2h. However, it doesn't explicitly state when not to use this tool or mention alternatives, though the sibling list shows many other list tools, so a slight deduction applies.

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