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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description contributes nothing further — it says nothing about whether traversal is recursive, whether files are returned alongside folders, how large listings paginate, or what happens with an invalid ref.

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 short sentence with no filler, so nothing is wasteful. The problem is the opposite of verbosity: it is under-specified for a six-parameter tool, and the one genuinely useful clause ('before selecting access') is buried at the end rather than front-loaded.

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?

Six parameters, five required, zero schema coverage, no output schema and no nested structure — the description needed to explain identifiers, ref formats and listing behavior, and instead repeats the title. An agent could not construct a correct call from this text without reverse-engineering the schema.

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% across six parameters, five of them required, so the description must carry the load and does not. 'branch or commit' loosely maps to 'ref' and 'folders' loosely to 'path', but company, environment, repositoryId and repository (two overlapping repo identifiers) are left entirely unexplained, including why both IDs are needed.

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 sentence names a verb and resource ('Browse repository folders') plus a scoping concept ('at a branch or commit'), so the general intent is graspable. But it is essentially a restatement of the title, and it never distinguishes this tool from nearby siblings such as summer_github_repositories_list or summer_github_sources_read, so an agent cannot tell which one to pick from the text alone.

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?

'before selecting access' is the only usage signal and it is an implied workflow hint rather than an explicit condition. No alternative tool is named, no prerequisites are stated, and there is no guidance on when this should not be used instead of the repositories/sources siblings.

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