langfuse-mcp-java

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

Description claims 'Read-only' which directly contradicts annotations (readOnlyHint: false, destructiveHint: true). Annotations indicate this is destructive and not read-only; description fails to disclose this dangerous behavior or explain why a list operation would be destructive.

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?

Two sentences, appropriately brief and front-loaded. However, the second sentence contains contradictory safety information, reducing utility.

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?

Fails to explain the destructive nature (per annotations), doesn't mention that both pagination parameters are required, and omits return format details. Incomplete for a tool with destructive behavior.

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 has 100% description coverage for both parameters (page, limit). Description adds no semantic value beyond schema, meeting the baseline 3 for high-coverage schemas.

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?

States specific verb 'List' and resource 'evaluation datasets' with scope 'in the Langfuse project'. Clear purpose but does not explicitly differentiate from sibling get_dataset or list_dataset_items.

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 no guidance on when to use this versus get_dataset (single retrieval) or list_dataset_items. No mention of required pagination parameters or prerequisites.

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