zda_account_settings

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Read-only', which implies safety but lacks detail on return format, potential size, or any side effects. For a read operation, more transparency about what 'account settings' entails (e.g., a single object, multiple fields) would be helpful.

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 is front-loaded and efficient. Every word adds value, specifying the resource and its read-only nature. There is no unnecessary information.

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 no output schema and no annotations, the description provides a reasonable overview of what the tool does and what it covers (branding, tickets, agents, etc.). It could mention that it returns all account settings in one go, but the listed examples give adequate context. The simplicity of the tool (no params) makes this sufficient.

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 has no parameters, so schema coverage is 100%. The description adds no parameter info, but none is needed. According to guidelines, 0 parameters yields a baseline of 4. The description's mention of specific included items provides some 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 'Read the Zendesk account settings' with specific examples like branding, tickets, agents. This distinguishes it from sibling tools that read specific resources (e.g., zda_get_group, zda_list_views). The verb 'Read' matches its read-only nature.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or situations where other tools like zda_list_brands or zda_list_ticket_fields might be more appropriate. The agent is left to infer usage from the name alone.

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