langfuse-mcp-java

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

Annotations mark this as destructive (destructiveHint=true), but description adds critical context: 'completely replaces the existing label set' (clarifies replacement vs append semantics) and the reserved 'latest' label warning. Also explains empty string behavior for removal.

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?

Five sentences front-loaded with purpose statement. Every sentence adds distinct value: purpose, replacement semantics, reserved label warning, required fields clarification, and empty string behavior. Zero waste.

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?

With destructive annotations, 100% schema coverage, and no output schema, the description adequately covers the operation's scope, constraints, and side effects. Missing only error handling details (e.g., prompt not found), which is minor.

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 coverage is 100% with all parameters well-documented. Description reinforces required status and empty string behavior, but primarily mirrors schema content. Baseline 3 is appropriate when schema carries the descriptive burden.

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?

Clear specific verb ('Replaces') with resource ('labels') and scope ('specific prompt version'). Distinguishes from sibling tools like create_prompt (creates new prompts), delete_prompt (removes prompts), and get_prompt (retrieves) by focusing specifically on label management for existing versions.

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?

Provides explicit constraints: 'The 'latest' label is reserved and managed by Langfuse — do not include it' (when-not guidance) and 'supply an empty string to remove all labels' (special usage pattern). Lacks explicit comparison to alternatives like create_prompt, but provides clear operational constraints.

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