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

With no annotations, the description carries full behavioral burden. It discloses the output format (headers, stripping of binaries/lockfiles/build dirs), token estimate presence, and filtering behavior. This is substantial, though it omits edge cases like size limits or error handling.

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 two sentences, front-loaded with the core purpose followed by behavioral details. Every phrase earns its place—no redundancy or filler.

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 accurately conveys the return format (context blob with headers, token estimate) and major options. With no output schema, this is sufficient. It lacks some depth on limitations (e.g., max repo size, include/exclude precedence), but the core usage is well covered.

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 100%, so the baseline is 3. The description adds practical value by explaining the purpose of include/exclude and max_tokens (focusing the repo and fitting a budget), which goes beyond the schema's property descriptions.

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 a GitHub repository and returns it as a concatenated text blob with headers, stripped binaries/lockfiles/build dirs, and a token estimate. This specific verb+resource+output format distinguishes it from siblings like get_file and list_files.

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 the use case (whole-repo aggregation with optional include/exclude filtering) and gives usage tips for globs and max_tokens, but it does not explicitly state when to prefer this tool over siblings or when not to use it. No alternative tools are mentioned.

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