zda_get_macro

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

The description correctly indicates a read operation ('Fetch') with no destructive side effects. No annotations exist, so the description carries the burden; it is truthful but does not disclose any specific authentication or rate-limit requirements.

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, front-loaded sentence with no filler words, efficiently conveying the essential purpose.

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 simple retrieval tool with one parameter, the description covers the core function and hints at the response ('full definition'). It does not document error scenarios or prerequisites, but this is acceptable given low complexity.

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 only parameter 'id' is fully described in the schema ('Numeric object ID'), and the description merely repeats 'by ID' without adding new semantic context 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 action 'Fetch a single Zendesk macro by ID' and distinguishes it from siblings like 'zda_list_macros' (which retrieves multiple) and 'zda_update_macro' (which modifies).

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 implies usage when a single macro's full definition is needed, contrasting with 'zda_list_macros'. However, it lacks explicit when-not-to-use or alternative conditions.

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