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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful auth context ('private repositories reuse the stored GitHub App connection') but says nothing about what the refresh actually does to the analysis, whether it is synchronous, or how long it takes.

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 short sentences with zero filler, leading with the action and scope and following with the auth note. Everything presented 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?

For a state-changing, open-world operation with no output schema, the description omits what the agent gets back (a job id, status, updated analysis) and whether the call blocks. The auth note helps, but the return and lifecycle story is missing.

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 67% and the entry for branch and context already carries detail; repo_id is undocumented in both schema and description. The description adds no branch or repo_id semantics beyond the existing fields, so baseline 3 fits.

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 verb and resource ('Refresh an existing repository analysis') plus scope ('at its latest commit'), which separates it from import_repository or get_repository. It stops short of naming which sibling to use instead, so an agent still has to infer the boundary.

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 phrase 'existing repository analysis' implies it only applies to repositories already imported and analyzed, but the description never says when to refresh versus re-import, fetch, or run repo_quality/repo_coverage. The branching guidance is left implicit.

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