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

Annotations already cover read-only, idempotent, and open-world traits, so the bar is lower. The description adds useful negative scoping ('does not close cases or send replies') and hints that it reaches out to GitHub, but says nothing about what the refresh check does, cost, or latency.

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, front-loaded with the core action and followed by the scoping caveat. Very little waste, though the second sentence is more about reassurance than specification.

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?

With no output schema and four undocumented parameters, the description should clarify what associations are returned and what the refresh option changes. It leaves both unanswered, so an agent cannot form an accurate call without guessing.

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 four parameters, so the description carries the full burden. It only gestures at the `refresh` toggle via 'optionally checking original GitHub state' and says nothing about company, environment, or case identifiers, leaving three required params completely opaque.

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: reading private engineering issue associations tied to cases. It is reasonably distinguishable from generic issue reads like summer_github_issues_read, though it doesn't explicitly say it scopes to a single case.

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 'optionally checking original GitHub state' implies when the refresh behavior is relevant, and 'Does not close cases or send replies' rules out mutation intent. But there is no explicit guidance on when to pick this over summer_github_issues_read or summer_cases_get.

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