langfuse-mcp-java

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

The description reinforces the destructiveHint=true annotation by explicitly stating 'This action is irreversible,' providing crucial user-facing context about permanent data loss; this adds value beyond the structured annotations by emphasizing consequence severity.

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?

Three sentences efficiently structured with purpose first, parameter format second, and critical behavioral warning third; no redundant language or extraneous details, with every sentence earning its place.

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?

For a single-parameter destructive operation with comprehensive annotations and no output schema, the description sufficiently covers core functionality, input requirements, and irreversibility; minor gaps include explicit sibling differentiation guidance and behavioral details for edge cases.

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 description coverage for traceIdsCsv, the schema already documents the comma-separated format and requirement; the description merely echoes 'Pass a comma-separated list' without adding format examples, validation details, or semantic nuances beyond the 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?

The description 'Deletes multiple traces in one request' provides specific verb (deletes), resource (traces), and scope (multiple/in one request), clearly distinguishing it from the singular delete_trace sibling present in the tool list.

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?

While 'multiple traces in one request' implies bulk operation distinct from the singular delete_trace alternative, the description does not explicitly state when to use this tool versus the singular variant or provide explicit exclusion criteria.

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