cases-load_context

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

No annotations provided, but the description discloses key behaviors: it loads data recursively (includes sub-cases), fetches items with content, and does it in a single call (efficiency). It does not explicitly state it's read-only or idempotent, but 'loads' implies no side effects. The lack of annotations is partially compensated.

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 sentences, no unnecessary words. First sentence states purpose, second provides usage guidance. Every part earns its place; it's highly 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?

No output schema, but the description specifies what is returned (case metadata, items with content, sub-cases). It explains parameters well and gives usage context. It does not cover error cases or permissions, but given the complexity (recursive load), it is sufficiently complete for a 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 100% (all parameters well-described). The description adds value beyond the schema: it suggests using depth 2+ for grandchildren, explains exclude_types default ['file'], and clarifies max_content_bytes 'keeps response manageable.' This provides actionable guidance.

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 clearly states it 'loads a case's full context in ONE call' including metadata, items, and sub-cases. It uses a specific verb ('loads') and resource ('case's full context'). It distinguishes from sibling tools by contrasting with multiple individual calls (cases-get + items-list + items-get).

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?

Explicitly tells when to use: 'instead of multiple cases-get + items-list + items-get calls when the user says "load this case into context" or similar.' This gives clear usage context and names alternatives.

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