lc_list_case_telemetry

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

The description only conveys a read operation but lacks any disclosure of behavioral traits such as authentication needs, rate limits, or side effects. Since no annotations are provided, the description carries full burden and falls short.

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 very concise (one sentence) and front-loaded, but it is overly minimal and lacks any structural elements like context or parameter hints. It is acceptable for a simple list tool but does not add value beyond the name.

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 requires two parameters with no schema descriptions and returns an unspecified output, the description is incomplete. It fails to explain what telemetry references are or how the parameters relate to the case, leaving ambiguity for the agent.

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 0%, and the description provides no explanation of what 'oid' or 'case_number' represent. The description adds no meaning beyond the parameter names, leaving agents to infer their roles.

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 the verb 'list' and resource 'telemetry references' with scope 'linked to a case'. It implicitly distinguishes from sibling tools that list other case-related items (e.g., artifacts, detections) by focusing on telemetry references.

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 like lc_list_case_artifacts or lc_list_case_detections. No prerequisites or context for use are provided.

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