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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds real value beyond them: the nonhidden-file restriction, the managed-area confinement, the account-bound computer:write OAuth requirement, and the possibility of a prompted local owner approval. It does not describe what metadata fields come back or any pagination, which keeps it from a 5.

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?

Three short sentences, front-loaded with the operation, followed by sibling routing and then the auth/approval constraint. Every sentence carries distinct information and there is no redundant restatement of the title.

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?

This is a simple two-parameter read whose annotations fully cover safety, and the auth prerequisites are disclosed. However, there is no output schema and the description never says what metadata is actually returned (size, timestamps, type), which is the core payload of a metadata-inspection tool and a meaningful gap for an agent deciding whether to call it.

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%, with the area enum and its allowed values plus the path semantics already documented in the schema. The description only echoes the scoping idea (named managed home area, nonhidden) without adding format or traversal detail beyond what the schema states, so the baseline 3 applies.

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?

Uses a specific verb (Inspect) against a specific resource (metadata for one nonhidden file) scoped to a named managed home area. It immediately separates itself from exza_list_home_files and exza_read_home_text by naming them, so an agent can pick this tool without opening the schema.

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?

Explicitly routes the agent: use exza_list_home_files to enumerate names or exza_read_home_text to obtain contents, which defines both the alternative tools and the condition selecting each. Nothing about when to invoke this versus those siblings is left to inference.

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