os_downloads_get_export

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description needs less behavioral disclosure. It does add the precondition 'previously prepared' and the retrieval-by-ID nature, but it does not explain what happens if the exportId is missing, expired, or how delivery/inlineMaxBytes affect behavior. This is acceptable but not rich.

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 a single front-loaded sentence with no filler. Every word contributes to meaning, and it is immediately clear what the tool does.

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 get-by-ID operation with an output schema and safety annotations, the description is nearly sufficient. The main gap is the missing explicit workflow context that this should be called only after os_downloads_prepare_export, and the semantics of delivery and inlineMaxBytes, which are needed to invoke the tool with full confidence.

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 0%, so the description must compensate. It only clarifies exportId as the retrieval key; delivery and inlineMaxBytes are left entirely unexplained despite having an enum and constraints. The parameter names and schema provide some hints, but the description adds minimal semantic value beyond them.

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 names a specific verb ('Retrieve'), a clear resource ('previously prepared OS downloads export'), and the lookup key ('exportId'). It does not explicitly name a sibling tool, but the phrase 'previously prepared' and the presence of os_downloads_prepare_export in the toolset make the distinction reasonably clear.

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 phrase 'previously prepared' implies that os_downloads_prepare_export must be invoked first, but this prerequisite is not stated explicitly. There is no guidance on when to choose this over alternatives or when not to use it, leaving the usage context to inference.

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