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

The annotations already declare the operation read-only, idempotent, open-world, and non-destructive. The description adds a tenant-ownership scope and a 'free' cost signal, which are useful, but it omits details like auth, pagination, or return behavior; annotations keep this acceptable.

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 description is one compact, front-loaded sentence that includes purpose and a cost note with zero filler. This is an ideal size for a simple one-parameter read.

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 read with strong annotations, this is minimally viable: the resource is named and the id is inferable. However, without output schema or return-format guidance, and with an ambiguous id, an agent cannot be fully confident about the call shape or result.

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?

With schema description coverage at 0%, the description must explain the single required 'id' parameter but never states what it identifies. The tool name and resource imply a case or observation ID, but the ambiguity is a real usability 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?

The description names a specific verb ('Read') and a specific resource ('tenant-owned case observations'), which distinguishes this tool from siblings like get_evidence or get_events. It clearly communicates what the operation does.

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 description provides no when-to-use guidance or exclusions and does not mention any alternative tool. The only contextual hint is 'tenant-owned,' which indicates scope but not selection criteria.

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