get_total_size

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

No annotations provided, so the description carries full burden. It only states 'Get total size' with no disclosure of behavior like whether it sums all matches, performance implications, or if there are limits on file count. Minimal transparency beyond the obvious read operation.

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 short and to the point, with an Args section that structures parameter info. It is not overly verbose, but the Args section could be integrated more cleanly. Overall efficient with no wasted words.

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?

Given the output schema exists (not shown), the description does not need to explain return values. However, with 15 sibling tools, the description does not help the agent differentiate when to use this specific aggregation tool. It is adequate but not fully comprehensive for a tool with multiple alternatives.

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%, but the description includes an Args section that briefly explains each parameter (query, folder_path, extension) as plain text. This adds some meaning beyond the bare schema, but the explanations are very generic and could benefit from more detail.

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 clearly states 'Get the total size of all matching files', which is a specific verb+resource. It distinguishes from sibling tools like search_files or get_result_count by focusing on total size rather than listing or counting.

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 guidance on when to use this tool versus alternatives like get_result_count or search_files. The description lacks any context about when it's appropriate or not, and does not mention potential limitations or prerequisites.

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