case_overview

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

Annotations declare destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally, and the description usefully enumerates the view's contents. However, readOnlyHint=false is left unexplained for what reads like a display operation, and no permissions, side effects, or scoping behavior are disclosed. Adds content context but no behavioral context beyond an already-sufficient annotation set.

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?

One front-loaded sentence enumerating the returned contents, with no filler, no hedging, and no repetition of the tool name. Every clause carries information.

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 simple one-parameter, no-output-schema tool, the content list gives the agent a reasonable picture of what comes back. It still omits what projectId scopes, whether the view is per-project or cross-project, and how it relates to the other project/review siblings, leaving gaps an agent would want filled before calling it.

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?

The single parameter projectId has 0% schema description coverage and is never mentioned in the description, so nothing explains that it selects which case is shown or what its format/constraints are. With one undocumented parameter and no compensating text, this falls below the baseline given to zero-parameter tools.

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 pairs a specific verb ('Show') with a named resource (the case overview) and enumerates exactly which artifacts are displayed: saved case question, accepted findings, review queue, contradictions, next steps. That is far more informative than a restatement of the name. It stops short of distinguishing this aggregate view from overlapping siblings like project_context, project_dossier, or project_export.

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 when-to-use guidance, no prerequisites, and no mention of alternatives, despite several siblings (project_context, project_dossier, review_record, project_export) that plausibly cover adjacent ground. The agent must infer from the tool name alone when this view is the right one to call.

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