extract_bc_snapshot

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

No annotations are provided, so the description carries full burden. It discloses that snapshots are ZIP archives containing .mdc and .al files, and that it returns a temp directory path. However, it does not mention any side effects (e.g., whether the original file is modified), authentication needs, or rate limits. Given the simple nature of extraction, this is adequate but not exceptional.

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, each serving a distinct purpose: first states action and content, second explains internal structure and return value. No extraneous text.

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 a single required parameter, no output schema, and no nested objects, the description is fully adequate. It covers what the tool does, what the snapshot contains, and what the output is (temp directory). No additional information is needed.

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 only parameter 'snapshot_path' is fully documented in the schema with a description ('Absolute path to the .snap file to extract'). The tool description adds no additional meaning beyond the schema, which has 100% coverage. Baseline score of 3 is appropriate.

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 verb 'Extract' and resource 'Business Central snapshot (.snap) file', and explains the purpose: 'to analyze debug traces, AL source code, and execution flow'. This distinguishes it from sibling tools like 'analyze_al_code' or 'ask_bc_expert' which are for analysis rather than extraction.

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 you need to extract a snapshot for analysis, but does not provide explicit guidance on when not to use it or alternatives. No exclusions or comparisons to siblings are given.

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