zdx_list_deeptrace_top_processes

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

Annotations already include readOnlyHint: true, so the description's 'Read-only' merely repeats that. It adds that it returns 'process groups' and the intent, but does not disclose output size, pagination, or any limitations. Since the read-only hint covers safety, the description's extra context is minimal but not contradictory.

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 two sentences, front-loaded with the main purpose, and each sentence adds value. It is efficient with no fluff.

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 list tool with two required parameters and no output schema, the description provides a general outcome ('process groups') but does not describe the returned record structure or the roles of trace_id/device_id. The query parameter's detailed schema helps, but the description itself is minimal, making it adequate but not fully complete.

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 description does not mention any parameters. The schema has only 33% coverage (only 'query' has a detailed description). The description should compensate by explaining trace_id and device_id, but it does not, leaving those parameters unexplained 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 ('List the top processes captured during a ZDX deep trace') with a specific verb and resource. It distinguishes from sibling tools like zdx_get_deeptrace_events or zdx_get_deeptrace_cloudpath by focusing on 'top processes' and 'process groups'.

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 a clear use case: 'useful for spotting resource-intensive processes impacting performance.' It does not explicitly compare with alternatives like zdx_get_deeptrace_events, but the context implies when to use it (when you need top processes from a deep trace). No exclusions are stated, but the mention of the purpose suffices.

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