langfuse-mcp-java

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

While annotations confirm destructiveHint=true and readOnlyHint=false, the description adds critical behavioral constraints: the irreversible nature of the action and the business logic distinction between custom and Langfuse-managed models. It does not contradict the openWorldHint or idempotentHint annotations.

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 to six sentences with minimal waste. The core action is front-loaded. Slight redundancy exists between 'Langfuse-managed models cannot be deleted' and 'Only custom models you created can be deleted,' though this serves emphasis for a destructive operation.

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?

Complete for a single-parameter deletion tool. Covers permission boundaries (custom vs managed), irreversibility warning, and override strategy. Absence of output schema is acceptable as the success/failure semantics of a delete operation are implicit.

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, the schema already fully documents modelId as required. The description states 'modelId is required' which merely duplicates the schema's required flag and description, earning baseline score 3.

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 opens with a specific verb and resource ('Deletes a custom model definition'), immediately clarifying scope. It distinguishes itself from sibling tools by specifying 'custom model' and contrasting with 'Langfuse-managed models,' helping the agent select correctly among create_model, get_model, and list_models.

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?

Explicitly defines when NOT to use ('Langfuse-managed models cannot be deleted') and provides a clear alternative ('To override a Langfuse-managed model, create a new custom model'). This directly guides the agent toward create_model for the override scenario instead of attempting this deletion.

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