or_zdr_endpoints

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

With no annotations, the description carries the burden. 'List' implies a read-only operation, and the explanation of ZDR adds context. However, it does not disclose any potential caveats such as authentication requirements, pagination, or whether the list is comprehensive or filtered, which would be useful for the agent.

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 sentence that states the purpose and expands the acronym without any filler. It is front-loaded with the action and resource, making it immediately scannable and efficient.

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?

For a zero-parameter tool with no output schema, the description covers purpose and usage context sufficiently. It could mention the return format (e.g., list of endpoints) or any access prerequisites, but given the simplicity, the description is mostly complete. The use case guidance adds important context beyond the bare action.

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?

There are zero parameters and the schema coverage is vacuously 100%. The description does not need to explain parameter meanings, and the baseline for zero-parameter tools is 4. No additional information is required.

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 uses the verb 'List' with the resource 'ZDR-compliant model endpoints', clearly stating the action and scope. The parenthetical expansion of the acronym adds precision, and the ZDR-compliance qualifier distinguishes this tool from siblings like or_model_endpoints.

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 phrase 'Useful for agents under privacy/compliance constraints' provides explicit context for when to use the tool. It does not mention alternatives or exclusions, but the sibling list implies a contrast with general model endpoint listings, so the guidance is clear enough.

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