Load a Shadow Monitor bundle

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

The description discloses format handling, reuse on same path unless reload=true, and the need for a passphrase. However, with no annotations provided, it omits potential side effects (e.g., memory usage), error conditions, or permission requirements. The level of detail is adequate but not exhaustive.

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 concise sentences: first states the core action and returns, second clarifies reuse and reload. Information is front-loaded and every sentence contributes meaningfully. No extraneous content.

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 no output schema, the description adequately covers input formats, return of bundleId and summary, and reload behavior. It does not detail the summary contents or error scenarios, but for a load tool these are secondary. The description feels comprehensive for typical use.

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 100%, but the description adds value beyond schema by explaining when `passphrase` is needed (encrypted bundles) and the `reload` parameter's effect on handle reuse. This enhances understanding of parameter usage.

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 loads and indexes a Shadow Monitor diagnostic bundle from a local file path, specifying supported formats (JSON, gzip, encrypted) and the return of a bundleId and summary. This differentiates it from sibling tools by positioning it as the entry point.

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 the bundleId is used by other tools, suggesting this should be called first, but it lacks explicit when-to-use or when-not-to-use guidance (e.g., 'use this before bundle_metadata'). No alternative strategies are mentioned.

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