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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds a scope ('household vault') and a level of detail ('metadata'), but says nothing about filtering, pagination, default behavior, or result limits. This is a minimal scoping statement above what annotations already provide.

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 a single concise phrase with no filler: 'Document metadata in the household vault.' It is front-loaded and easy to parse. While it may be under-specified, as a concise statement it is well structured and free of redundancy.

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?

Despite having an output schema and safety annotations, the description leaves out essential context: what the filter parameters mean, how the tool relates to get_document, and what 'metadata' includes. With five optional parameters and many sibling tools, a one-line fragment is insufficient for an agent to invoke the tool correctly.

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%, so the description must compensate for the five undocumented parameters. It does not explain limit, status, category, domain, or household_id, beyond a loose hint that 'household vault' relates to household_id. An agent would have to rely on parameter names and defaults alone to infer 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 names a specific resource ('document metadata') and a scope ('household vault'), which helps distinguish it from sibling tools like list_accounts or list_facilities. However, it is a noun phrase rather than an explicit action statement; the verb 'list' is only present in the tool name and title, not the description itself.

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?

No usage guidance is provided. The description does not state when to prefer list_documents over alternatives such as get_document, nor does it mention exclusions, prerequisites, or the appropriate context for using this tool. An agent must infer usage entirely from the name and title.

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