lc_list_case_orgs

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

No annotations provided, but the tool is a simple read operation with no side effects. The description adequately implies it returns a list of organizations accessible to the caller, which is sufficient for this straightforward tool.

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?

Extremely concise single sentence that directly states the tool's purpose. No wasted words.

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 exists, and the description does not mention what the returned data contains (e.g., IDs, names). For a simple listing tool, this is a minor gap. The tool is still usable but lacks full 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?

The tool has zero parameters, so baseline score is 4 per guidelines. The description does not add parameter semantics as none exist.

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 lists 'ext-cases organizations accessible to the caller', using a specific verb and resource. It distinguishes from siblings like 'lc_list_orgs' by specifying 'ext-cases' and 'accessible to the caller'.

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?

No guidance on when to use this tool versus alternatives such as 'lc_list_orgs' or 'lc_get_org_info'. The description only states what it does, without any when-not or contextual cues.

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