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

Annotations already declare this a safe, idempotent read, so the bar is lower, and the description still adds real behavior: only approved public cases are visible, and withdrawn ones fail as not found. It omits auth requirements and the shape of the returned case, so it is helpful but not exhaustive.

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 tight sentences, zero filler, with the visibility scope stated before the failure mode. 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?

With no output schema, the description could do more to describe the returned case, and it never mentions permissions. It does cover the two things most likely to trip an agent — visibility restriction and withdrawn-case failure — which is solid for a one-parameter read tool.

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% and the single 'id' parameter has no documented format or provenance. The description implies the id selects a specific case, which makes the intent self-evident, but adds no syntax or constraint detail to compensate for the coverage gap.

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 ('Read one approved public case') and adds a governing qualifier ('approved public') that visibly separates it from list_cases and from retrieval siblings like get_offer/get_task. An agent can identify what it retrieves without opening the schema.

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?

Usage is implied by the name and by the single-case scope, and the not-found condition for withdrawn cases gives one useful boundary. However, it never explicitly says when to reach for this over list_cases or how to obtain a valid id, leaving selection to inference.

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