huddo_files

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value beyond that: ordering ('newest first'), the returned fields, and the fact that local paths only appear for already-downloaded files. It doesn't discuss pagination or identity-scoped behavior, but the annotation bar is already met.

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?

Two sentences, front-loaded with the core listing behavior, then a pointed follow-up hint. Every clause earns its place with no filler.

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?

With no output schema, the description usefully enumerates what is returned (attachment, message, sender, local path) and the ordering. It leaves pagination/limit interaction and identity scoping to the schema, which is acceptable given 100% schema coverage, but a touch more on result shape 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 description coverage is 100%, so all six parameters (as, from, room, type, limit, query) are already documented with defaults and formats. The description adds no parameter-level detail beyond mentioning msgid, so 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?

States a specific verb ('List') and resource ('attachments in your rooms (or one room)') and even previews the return shape (message, sender, local path). An agent can distinguish this from huddo_read or huddo_search without opening any 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 follow-up action: 'Use huddo_download with the msgid to save one.' This is clear context for what to do next. It stops short of naming when to prefer huddo_search or huddo_read for other file-related exploration, so it is not a full 5.

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