Get repository blob

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable context about encoding: UTF-8 text is decoded by default and binary content remains bounded base64. This goes beyond the annotations and informs the agent about response formatting.

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 compact sentences, no filler. The first sentence states the purpose, the second adds necessary behavioral detail. Every word earns its place, and the description is front-loaded with the primary action.

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?

The description covers core behavior (fetching by SHA, decoding rules) and is supported by strong annotations and an output schema. Minor gaps remain (e.g., role of max_bytes, meaning of 'bounded base64'), but overall it is sufficiently complete for a read-only blob retrieval tool.

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 only 25%, so the description must compensate. It explains blob_sha via 'by Git object SHA' and decode_text via 'UTF-8 text is decoded by default'. However, max_bytes is not mentioned at all, leaving its behavior unclear. Partial compensation is provided.

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 the tool fetches repository blob content by Git object SHA, using a specific verb ('fetch') and resource ('repository blob'). It distinguishes from sibling tools like get_file (which likely fetches by path) by emphasizing the SHA-based access.

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 implies when to use this tool (when you have a Git object SHA), but it does not explicitly mention alternatives or exclusion scenarios. Sibling tools like get_file or search_code are not referenced, so the guidance is only implicit.

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