import_xctrace

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description needed to clarify the mutation/import side effects. 'Preserve' suggests non-destructive storage, but the description does not disclose what gets written, whether existing artifacts are replaced, or how the 'bounded' export limit behaves. No contradiction with annotations, but meaningful behavioral context is missing.

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 efficient sentence with no filler or repetition. It front-loads the primary action and resource. The brevity is a virtue here, though some precision is sacrificed.

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 tool with three parameters, one required, and many closely related siblings, this description is too sparse to fully orient an agent. An output schema exists and may explain return values, but the description still omits how the bounded export is produced, where it is stored, and what distinguishes this import path from generic artifact import or extract_* tools.

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 description coverage is only 33%, with max_export_bytes and source_root lacking descriptions. The phrase 'bounded xctrace TOC export' obliquely refers to the export-size limit, but it never explicitly maps to max_export_bytes, and source_root is left completely unexplained. The description does not compensate for the schema's low 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 names a specific resource ('native Metal trace bundle') and a clear action ('Preserve'), with a distinct artifact type ('bounded xctrace TOC export') that helps separate it from generic import/extract siblings. However, it does not explicitly contrast with tools like import_artifact or the many extract_* analogues, so differentiation is mostly inferred from the Metal/xctrace specifics.

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 gives no guidance on when to use this tool versus the many sibling import/extract tools. It does not mention prerequisites, intended capture/export scenarios, or cases where another tool would be more appropriate. The phrase 'preserve a ... bundle' implies an archival use case but does not make it actionable.

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