decode_blob

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'read-only' is redundant. It adds 'bounded' which hints at limit/offset behavior, and 'archive retrieval' provides context about the data source. However, it does not disclose error behavior, pagination semantics, or what exactly 'decode' entails. With annotations covering safety, the description adds marginal value.

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 zero waste. It immediately states the verb and resource, then adds a concise qualifier. It earns every word and is appropriately brief for a simple tool.

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 tool with no output schema and three parameters, the description is insufficient. It does not clarify what a blob is, what 'decode' produces, how hash relates to a blob, or the meaning of limit/offset. Given the sibling 'get_blob', the agent may confuse the two. The description lacks critical information needed to call 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 description coverage is 0%, and the description does not explain any of the three parameters (hash, limit, offset). The term 'bounded' vaguely suggests limit/offset, but the agent receives no clarity on what 'hash' refers to, what units limit/offset use, or their effect. The description fails to compensate for the lack of schema documentation.

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 'Decode blob; bounded read-only archive retrieval' – a clear verb ('decode') and resource ('blob') with a clarifying qualifier ('bounded read-only archive'). It distinguishes from the sibling 'get_blob' by implying decoding rather than raw retrieval, though it does not explicitly name an alternative. This is clear but not maximally differentiated.

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 offers no guidance on when to use this tool versus siblings like 'get_blob', 'search', or 'query'. There is no mention of conditions or exclusions. The phrase 'bounded read-only' implies a read-only context, but it does not specify when to choose this over other retrieval tools.

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