get_blob

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

No annotations are present, so the description carries the full behavioral burden. It does disclose that the returned data is base64-encoded, which is useful, but it says nothing about required permissions, size limits, error behavior, or whether missing blobs return null versus an error.

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?

It is a single sentence, but it is under-specified rather than concise. The 'Extended:' prefix is unexplained and the phrase 'GetBlobForAgentKV one record blob' is grammatically awkward, so the one sentence does not earn its place.

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 two-parameter read tool with no annotations and no output schema, the description should explain what a blob is, how to obtain bcId/blobId, and what exactly comes back. It only hints at base64 data, leaving the agent without enough context to use the tool confidently.

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 100% and there are only two parameters, so the baseline is 3 even without description-level parameter detail. The description adds no meaning beyond the schema for bcId or blobId, but the schema already documents both.

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 verb and resource ('GetBlobForAgentKV one record blob') and notes the return payload is base64 blob_data. However, 'one record blob' and 'GetBlobForAgentKV' are opaque, and it does not differentiate this tool from near-siblings like read_store_file or get_artifact_url. Adequate but vague.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling tools. An agent cannot infer from the text whether this is the right blob-fetching tool or when to prefer it over read_store_file.

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