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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, yet the description adds real value beyond them: no credit consumption, and a hard scope boundary limiting reads to scene attributes rather than people. The repetition of 'read-only' is redundant, but the cost and scope disclosures are substantive additions the annotations do not carry.

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?

The purpose is correctly front-loaded in the first clause, but the prohibition against identifying people is restated three times ('never the people in it', 'no face recognition, no biometric identification, no person matching', 'never who is in it'). Those guardrails matter, yet the redundancy dilutes an otherwise tight definition.

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 single-parameter, read-only tool with no output schema, the description adequately conveys what comes back — a summary of case contents, attached results and their targets — plus the operational and ethical limits. Nothing essential to correct invocation is missing, though an explicit pointer to a sibling for deeper analysis would round it out.

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?

Only one parameter, and the schema already documents case_id with its source (list_cases or create_case) at 100% coverage. The description adds no format, validation or edge-case guidance about the id, so the schema does all the work — the baseline of 3 applies.

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 a case's summary — and enumerates the contents (what the case holds, attached results, where they point). The read-only framing implicitly separates it from analyze_case_image and geolocate_image, but no sibling is named explicitly, so routing still requires inference.

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?

Gives clear usage context through exclusions: it never runs an analysis and never spends credits, which steers the agent away from it when computation is wanted. It stops short of naming which sibling to call instead (e.g. analyze_case_image, list_analyses), so the alternative is implied rather than stated.

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