panelica_file_manager_get_v1_files_trash_stats

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

Annotations already mark the call read-only, idempotent, and non-destructive, and the description adds the needed OAuth scope 'files:read' and repeats 'Read-only' as a safety signal. It does not document response format, but the safety profile is well covered.

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 compact and front-loaded with the operation before metadata. Minor redundancy exists ('Read-only' and category appear alongside annotations/title), but there is no padding.

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 read-only call with strong annotations, the description is serviceable, but it never says what the trash statistics contain or how the response is shaped. Since there is no output schema, a bit more return-value context would make it complete.

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 coverage is 100%, and the schema describes 'user_id' as 'Target user ID', which is adequate for a single obvious parameter. The description adds no extra meaning about what the user_id scopes the statistics to.

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 clear verb+resource ('Get trash statistics') and the HTTP path '/v1/files/trash/stats' reinforces the specific operation. It is distinct enough from sibling `get_v1_files_trash` (list vs stats), though it does not explicitly spell out that distinction.

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 gives no guidance about when to choose this over the trash list, restore, or empty endpoints. It only states the endpoint, category, and required scopes, so an agent must infer usage context from the tool name and siblings.

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