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

Annotations already declare read-only, non-destructive, and closed-world behavior, but the description adds useful context: the output is an offline HTML file to save, the inventory is not stored, and the tool performs rendering only. It does not describe size limits or validation failures, but it meaningfully extends the annotation coverage.

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 front-loads the core transformation and stays focused on what the tool does, what it returns, and what it does not do. The filename example and field guide link are useful, though the description is slightly longer than necessary for its level of parameter detail.

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 complex renderer with seven required parameters and no output schema, the description explains the output type and stateless behavior. It does not explain the expected input structure or validation rules, leaving much of the complexity to the external field guide and schema.

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 0% across seven required nested parameters. The description conveys high-level content such as connections, reads/changes, approvals, riskiest powers, and trimmable items, but it never explains key fields like version, drawn, checks, or unseen, nor does it clarify the many enums and constraints, so an agent still cannot reliably format most of the input.

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 states a specific transformation ('Turns an agent's own inventory... into... a single offline HTML page') and a clear artifact, so its purpose is easy to identify. It does not distinguish itself from related siblings such as check_agent_one_page, leaving some ambiguity about which tool to choose.

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 implies usage when an agent has an inventory and wants a visual access map, and it clarifies that the tool only draws rather than collects data. However, it gives no explicit when-to-use guidance versus siblings, no prerequisites, and no exclusions.

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