langfuse-mcp-java

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

Description claims 'Read-only' but annotations specify readOnlyHint=false and destructiveHint=true, indicating mutation/deletion capabilities. This is a dangerous contradiction. Description mentions pagination but fails to clarify destruction behavior that annotations indicate.

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?

Brief two-sentence structure is appropriately concise, but both sentences contain inaccuracies (false optionality claim, read-only contradiction) that waste the agent's time and risk harmful invocations.

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?

Missing output schema explanation (what session data returns?), no differentiation from similar list tools, and contains critical safety misinformation. Incomplete for a tool with destructive annotations that claims to be read-only.

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% coverage (baseline 3), but description incorrectly characterizes timestamp parameters as 'optional' when schema marks them required. Mentions 'paginated' implying page/limit usage but doesn't add syntax guidance beyond schema.

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 action (list) and resource (sessions) with scope details (paginated, time range). However, claims time range is 'optional' when schema marks timestamps as required, and fails to distinguish from sibling tools like get_session_details (singular) or get_user_sessions (user-scoped).

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 versus alternatives like get_session_details or get_user_sessions. No mention of prerequisites, authorization requirements, or when the time range filter is necessary versus fetching all sessions.

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