get_case_observables

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

Describes sorting, date filtering, and default limit. No annotations exist, so description carries full burden. Could mention non-destructive nature, but overall adequate.

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?

Structured list of parameters, front-loaded with purpose. Slightly verbose with 'Args:' but overall clear and efficient.

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?

Covers all 5 parameters for a list tool with output schema. Minor inconsistency: 'List all' vs 'Maximum number'. Adequate for the context.

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 has 0% description coverage, so description fully explains each parameter: case_id as unique ID, sort with '-' prefix, date filters as ISO 8601/timestamps, limit with default 50.

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?

Clearly states 'List all observables associated with a specific Case' with a specific verb and resource. Distinct from sibling tools like get_case or get_case_tasks.

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?

Implies usage for retrieving observables for a case but lacks explicit when-to-use vs alternatives like search_cases or get_case. No exclusions or when-not guidance.

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