dooray_post_files

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

With no annotations, the description fully carries the behavioral disclosure burden. It reveals that the endpoint can return an empty result or AUTH_FORBIDDEN_ERROR even when files are accessible, which is a critical non-obvious behavioral trait. This goes well beyond what the input schema or annotations could convey.

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?

Three sentences, each earning its place: the action, the exclusion, and the critical failure-mode warning. The key caveat is front-loaded rather than buried.

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?

The description covers the essential behavioral caveat and the distinction from sibling tools, making it usable with the schema-covered parameters. It does not describe the exact return format, but for a list operation this is a minor gap given the strong guidance already provided.

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 the schema already documents all three parameters adequately. The description adds no parameter-specific details beyond labeling the result scope, so the baseline 3 is appropriate.

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 phrase 'List regular attachments only' gives a specific verb, resource, and scope, immediately distinguishing this from dooray_post_file_download and from checking inline body images in dooray_posts.fileIdList. It is not a tautology and the sibling differentiation is explicit.

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 clearly states when not to use this tool, explicitly warns against using it as an availability check, and mentions dooray_post_file_download as the alternative that may still succeed. This gives an agent concrete routing guidance.

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