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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it only states the operation without mentioning read-only semantics, error cases, default ref behavior, or response format. The 'github_readonly' prefix hints at safety, but the description itself adds no behavioral context.

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?

A single front-loaded sentence states the complete purpose with no filler words. It is appropriately sized for a straightforward resource access operation.

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 schema covers parameter semantics well, but the absence of annotations and an output schema leaves the description as the sole behavioral guide. It fails to mention return shape (e.g., whether file content is raw or encoded) or default ref semantics, which an agent would need for fully correct invocation.

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%, so the parameters are already fully documented in the input schema; the description contributes no additional meaning about owner, repo, path, ref, sha, or fields. A baseline 3 is appropriate since the description does not need to compensate for schema gaps.

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?

States a specific action ('Get the contents') and a precise resource ('a file or directory from a GitHub repository'), which clearly distinguishes it from sibling tools that target user info or pull requests. The verb/resource combination leaves little ambiguity.

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 provides no explicit when-to-use guidance or comparison with alternatives such as github_readonly.get_me or github_readonly.pull_request_read. The intended use is only implied by the resource referenced, so an agent must infer when this tool is appropriate.

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