environment_snapshot

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

Beyond the readOnly and non-destructive annotations, it discloses the grant model, that requests cannot grant consent, that approval of this call is not a grant, that denied/unsupported/unavailable results include reasons, and that each observation records its basis. This is unusually rich behavioral context for a read-only diagnostics tool.

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 dense and front-loads usage guidance before a crisp statement of purpose. The grant-threat-model details are relevant, but several sentences repeat or expand on concepts already covered by annotations and schema, making it longer than necessary.

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?

It covers the important behavioral boundaries: grants, protected policy, denial reasons, basis, and read-only operation. With no output schema, it does not fully specify the return shape beyond basis and unavailable observations, but it gives enough context for correct invocation.

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 100%, and the schema already documents list, path, task, tools, and categories. The description's parameter-related statements mostly restate the schema, such as list: true naming categories and task granting nothing, rather than adding substantial new parameter-level semantics.

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 uses a specific verb and resource: observe parts of this machine, collecting diagnostics categories only and never files or reports. It is clear about the tool's purpose, but it does not differentiate it from the sibling tools snap, source_text, summary, or verify_report.

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?

It explicitly says to use this before giving system-specific instructions such as install commands, drivers, or setup, and to ask only for the categories the task needs instead of guessing. It does not state when to choose a sibling tool or when not to use this one.

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