langfuse-mcp-java

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

Adds valuable safety context beyond annotations by stating 'This action is irreversible,' reinforcing the destructiveHint. However, it omits implications of idempotentHint=false (what happens on re-invocation) and openWorldHint=true, and doesn't mention cascade effects or error cases (e.g., trace not found).

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 with three short sentences. Front-loaded with the primary action, zero redundancy, and every sentence earns its place—the irreversibility warning is critical for a destructive tool.

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?

Adequate for a simple single-parameter deletion tool. Captures the destructive nature and required parameter. Could be improved by noting the response behavior (e.g., void/empty on success) or 'not found' error conditions, but acceptable given the low complexity and presence of annotations.

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?

With 100% schema coverage, the schema already fully documents the traceId parameter. The description merely repeats 'traceId is required,' adding no semantic depth, syntax examples, or format guidance beyond the structured schema definition.

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?

Specific verb (Deletes), resource (trace), and scope (single by ID) clearly stated. The 'single' qualifier effectively distinguishes this from the sibling 'delete_traces' (batch deletion) without needing explicit naming.

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 provided on when to use this single-trace delete versus the sibling 'delete_traces' for batch operations, nor any prerequisites or conditions. Only states parameter constraints ('traceId is required'), not usage context.

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