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

Annotations already declare readOnly=true, idempotent=true, openWorld=true and destructive=false, so safety is covered. The description adds useful negative context — it does not establish identity, link cases, invoke a model, or start work — which tells the agent the similarity is not LLM-derived and the call has no downstream effects. It still omits result shape and pagination/'bounded' semantics.

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 no filler, leading with the primary operation before the exclusions. Slight inefficiency in that the negative clause consumes half the budget while core parameters go unexplained.

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 four-parameter, three-required tool with zero schema descriptions and no output schema, the definition leaves too much unspecified. An agent cannot tell what 'case-summary text matches' returns, how company/environment scope the query, or when this beats summer_cases_search.

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%, so the description must carry the burden for all four parameters, yet it never mentions company, environment, case, or limit. Only the word 'bounded' hints at the limit parameter; the unconstrained UUID fields and the staging/production enum receive no explanation.

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 names an action (read/list) and a resource (case-summary text matches), so the general intent is recoverable. However, phrases like 'source observation and matching terms' are internal jargon, and nothing distinguishes this from siblings such as summer_cases_search or summer_cases_get beyond the tool name.

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?

There is no statement of when to use this tool or which sibling to pick instead. The second sentence lists exclusions ('does not establish customer identity, link cases, call a model or start work'), but these describe non-effects rather than routing guidance, so an agent still cannot decide between this and summer_cases_search.

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