xctrace_export

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

No annotations are provided, so the description carries the full burden. It states the tool exports data but does not disclose behavioral traits such as whether it is destructive, authorization requirements, or error handling. The return value is vaguely described as 'Exported data or success message.'

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 concise with a clear lead sentence followed by a parameter list. Each sentence serves a purpose, though the parameter descriptions are minimal. It is front-loaded and efficient.

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 tool has 4 parameters, required input_file, and no annotations, the description is incomplete. It lacks information on error conditions, environment prerequisites (e.g., Instruments installation), and behavioral details like file size limits. The presence of an output schema mitigates the need for return value details, but overall context is insufficient.

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?

With schema description coverage at 0%, the description provides basic explanations for each parameter (e.g., 'Path to the .trace file to export from'). These add meaning beyond the schema's bare titles but lack details like format constraints or relationships.

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 'Export data from an Instruments trace file,' specifying the verb (export) and the resource (Instruments trace file). This distinguishes it from sibling tools like xctrace_import, xctrace_list, and xctrace_record.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context. Sibling tools exist (e.g., xctrace_import, xctrace_record), but no differentiation is offered.

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