td_storage_overview

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

No annotations are provided, so the description must signal safety. The verb 'Get' and the word 'overview' strongly imply a read-only aggregation, and the output scope is stated as 'file counts and sizes per dialog'. It does not detail side-effect absence, permission needs, or behavior when the limit truncates dialogs, but nothing contradicts the read-only implication.

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 entire description is one front-loaded sentence with no filler. It names the action, resource, and output in eleven words, every one of which earns its place.

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 one-parameter tool with no output schema, the description gives the essential return concept and the schema covers the limit parameter. It lacks explicit return formatting or ordering, and it does not mention how truncation affects completeness, but an agent can still infer what invoking it will yield.

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?

The only parameter, limit, is fully described in the schema ('Max dialogs to scan for storage stats'), so the description adds no new parameter meaning beyond the structured data. With 100% schema_description_coverage, the baseline of 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?

The description uses a specific verb ('Get') and resource ('storage overview') and specifies the output ('file counts and sizes per dialog'). It is distinguishable from sibling file-listing and search tools because it is an aggregate summary rather than a file-level operation.

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 establishes a clear context: use when you need a high-level storage summary per dialog. It doesn't explicitly name alternatives or state when not to use it, but the overview framing implies the contrast with file-level tools like td_list_files and td_search_files.

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