download-bytes

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation. The description adds value by specifying the return format (contentType, encoding, contentLength, contentBytes) and that it returns base64, consistent with the read-only nature. No contradictions.

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 extremely concise: two sentences that front-load the purpose and return format, followed by a bullet-like list of use cases and the return object shape. No extraneous information.

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 complexity of binary downloads from various Microsoft Graph endpoints and the absence of an output schema, the description adequately covers return format, use cases, and an alternative for large files. Minor gaps like error handling or size limits do not significantly detract from completeness.

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% with a very detailed parameter description covering many common paths. The description adds overall context but does not significantly enhance parameter semantics beyond the schema, leading to a baseline score of 3.

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 clearly states it downloads binary content from Microsoft Graph and returns base64. It explicitly lists multiple use cases (drive files, mail attachments, profile photos, Teams content, meeting recordings) and distinguishes from the sibling tool get-meeting-recording-content for large files.

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 provides explicit guidance: it is a single tool for any binary read, and specifically advises against using it for large meeting recordings, directing to an alternative tool. The schema's parameter description also lists many common paths, aiding correct invocation.

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