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

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is partly covered. The description adds useful behavioral context about cache reuse for unchanged commits and GitHub not being pulled at sandbox startup. It still does not clarify what happens to the existing cache when the commit changes or what a destructive refresh actually replaces.

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 short sentences with the main action front-loaded. The second sentence adds useful operational context without wasting space. Every sentence earns its place.

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?

This is a destructive, open-world sync operation with four parameters, no output schema, and only 25% schema description coverage. The description covers the high-level action and cache reuse but leaves required parameters, response behavior, and the consequences of a destructive cache refresh unexplained. It is not sufficient for an agent to invoke the tool confidently without additional inference.

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 only 25%, so the description should compensate for undocumented parameters. It only vaguely maps to source_id through 'selected repository' and does not explain company, environment, or how idempotency_key should be used. The description adds little meaning beyond the schema names.

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 a specific verb and resource: refreshing the selected repository code cache from GitHub. It clearly differs from sibling tools such as summer_github_sources_read and summer_github_sources_save, though it does not explicitly name those alternatives. The core action is unambiguous.

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 the tool matters by noting cache reuse for unchanged commits and that sandbox startup never pulls GitHub. However, it does not explicitly say when an agent should invoke this sync versus read or save operations, nor does it give prerequisites or exclusions. Usage is inferable but not directly stated.

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