get_case

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It merely states 'Get case details' without revealing return format, error behavior, permissions, or whether the operation is read-only. This is a minimal disclosure that leaves significant behavioral aspects unknown.

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 extremely concise, with no unnecessary words. However, it is under-specified to the point of not earning its place as a useful description. It is a single phrase with no structure or additional information, which is more under-specification than effective conciseness.

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?

Given the tool has three parameters, no annotations, and an output schema not visible to the agent, the description is incomplete. It does not explain what 'details' includes, how to construct a request, or any nuances about regions or required fields. The presence of many sibling tools makes this incomplete context more problematic.

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 input schema has zero description coverage for all three parameters (domain_id, case_id, region), and the description does not mention any parameters or their meanings. The description fails to compensate for the lack of schema descriptions, leaving parameter semantics entirely inferred from names.

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 'Get case details' clearly identifies the action and resource. However, it does not distinguish this from sibling tools like search_cases or cases_get_template, which also relate to case retrieval. It lacks scope specifics such as fetching by case_id, but the name provides some clarity.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or how it differs from search_cases or cases_list_cases_for_contact. The one-sentence description offers no contextual usage information.

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