xctrace_list

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

No annotations exist, so the description must disclose behavior. It only states the function and return type, but does not mention idempotency, safety, authorization needs, or side effects. A read-only hint is implied but not stated.

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?

Two sentences plus an Args/Returns block. No extraneous text, front-loaded purpose, and efficiently structured. Every sentence adds value.

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 one parameter and an existing output schema, the description explains the param and return type. It omits potential constraints like requiring Xcode or offline mode, but for a simple list tool this is nearly 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?

Schema coverage is 0%, so the description must explain the parameter. 'list_type' is described with allowed values ('devices', 'templates', 'instruments'), adding meaning beyond the schema's bare string type. Could optionally note the default if any.

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 tool lists 'devices', 'templates', or 'instruments', specifying the verb 'list' and the resource categories. It distinguishes from siblings like xctrace_record (recording) and xcodebuild_list (Xcode build lists) by explicitly naming the scope.

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 guidance on when to use this tool versus alternatives (e.g., xcodebuild_list for Xcode-related listings). The description lacks explicit context for selection, such as prerequisites or conditions.

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