get-loop-component-content

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description adds useful context beyond them: the content is raw Fluid/JSON-like text and filename helps with text decoding. This is meaningful behavioral detail for an agent deciding whether and how to invoke the tool.

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 carry the full meaning with no redundancy. The most important selection information (what and how) is front-loaded, and the content format note is placed at the end without bloating the description.

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?

For a simple read-only download tool with strong annotations, the description covers the essential agent needs: what is returned, how to identify the target, and where the identifiers come from. No output schema exists, but the content-format hint compensates for that gap.

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?

The input schema already describes all parameters, so the baseline is 3. The description adds valuable semantic provenance by explaining that driveId and itemId come from a search-loop-components hit's resource.parentReference, which is beyond the schema's simple 'Value for driveId' phrasing.

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 states a specific verb ('Download'), a specific resource ('Loop component's raw content'), and the exact identifiers needed, while distinguishing this from generic drive downloads by noting the Fluid/JSON-like text format and its origin in search-loop-components. It clearly separates this tool from sibling tools like download-drive-item or get-drive-item.

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?

It gives clear context for when to use this tool: after search-loop-components, using driveId and itemId from resource.parentReference. It does not explicitly name alternatives or state when not to use it, but the source-specific guidance is strong enough to route an agent correctly.

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