public_access_download

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

No annotations provided. Description mentions 'public route' but lacks details on behavior such as response format, file size limits, error handling, or whether it returns binary data or a URL. The agent is left guessing about important behavioral traits.

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?

Single, concise sentence that contains essential information. No extraneous text. However, could be slightly longer to include parameter details without losing clarity.

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?

No output schema and minimal description. For a download tool, the agent needs to know what the output is (e.g., file content or path). Missing details about save_path behavior and default connection. Incomplete for effective use.

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 33% (only content_id described). Description adds that content_id is an attachment ID and mentions the endpoint pattern, but save_path and connection parameters are unexplained. Does not fully compensate for low schema coverage.

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?

Clearly states 'Download attachment/binary content by ID', specifying the action and resource. The mention of 'Public route' distinguishes it from authenticated download tools like odoo_attachment_download.

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?

Implies usage for downloading attachments without authentication via the public route, but does not explicitly state when to use this vs. alternatives (e.g., odoo_attachment_download). No when-not or exclusion criteria provided.

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