zernio_get_ads_tree

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

No annotations are provided. The description indicates a read-only operation (getting a hierarchy), but lacks details on authentication requirements, rate limits, or the exact structure of the returned tree. It meets basic expectations for a get tool.

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 unnecessary words. Every part earns its place.

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 single optional parameter, no output schema, and the presence of sibling tools, the description is largely complete. It could benefit from briefly stating the hierarchy structure (e.g., accounts contain campaigns, campaigns contain ads), but it is 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 input schema provides 100% coverage for the single optional parameter 'accountId', described as 'Filter by ad account ID'. The description does not add extra semantic information beyond the schema, so it meets the baseline for high schema coverage.

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 specifies the verb 'Get', the resource 'full hierarchy of ad accounts, campaigns, and ads', and the scope 'in a single call'. It effectively distinguishes from sibling tools like 'zernio_list_ad_accounts' or 'zernio_get_ad' which retrieve flat lists or single items.

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 the full hierarchy is needed in one call, contrasting with siblings that fetch individual components. However, it does not explicitly state when not to use it or name alternatives.

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