microsoft_download_file

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions routing infrastructure but does not state whether the operation is read-only, destructive, or has any side effects. It also omits error handling, permissions, or response details. The description fails to compensate for missing annotations.

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 but wastes space on routing details (JWT, tenant, company scope) that are implementation-specific and not helpful for usage. It is structured but not concise in a value-adding way.

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 tool has one parameter, no annotations, and an output schema (unseen), the description should explain what the tool downloads, required arguments, and expected return. It is incomplete, leaving the agent without enough context to use the tool correctly.

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 0%, so the description must compensate. It states that 'arguments' is a JSON string but does not specify what keys or values are expected (e.g., file ID, path, format). This adds minimal meaning beyond the schema itself.

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 name 'download_file' suggests downloading a file from Microsoft services, and the description mentions 'Microsoft connector operation'. However, it does not specify which Microsoft service (OneDrive, SharePoint, etc.), what kind of files, or how it differs from siblings like microsoft_upload_file. Purpose is vaguely stated but not fully clarified.

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 vs alternatives (e.g., microsoft_upload_file, microsoft_update_file). No prerequisites or context for usage are provided, such as needing a file ID or path.

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