langfuse-mcp-java

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

The description explicitly states 'Read-only' which directly contradicts the annotations (readOnlyHint: false, destructiveHint: true). This misrepresents the tool's safety profile and potential side effects, creating a serious risk of misuse.

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?

The description is extremely concise at only two short sentences. However, the second sentence ('Read-only.') wastes its place by stating false information, preventing a perfect score.

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 destructiveHint:true and no output schema, the description fails to explain what state changes occur (what gets destroyed) or what data structure returns. The contradiction regarding read-only behavior leaves the agent without accurate behavioral context.

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%, so the schema fully documents all three parameters (userId, page, limit). The description mentions 'pagination' and 'specific user', providing minimal semantic mapping but not adding syntax details or validation rules beyond the 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?

The description clearly identifies the resource (sessions), the scope (for a specific user), and the mechanism (pagination). However, the claim of being 'Read-only' creates confusion given the contradictory annotations, slightly diminishing clarity.

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?

No guidance provided on when to use this versus sibling tools like 'fetch_sessions' or 'get_session_details', nor when to stop paginating. The only usage hint is 'pagination', which merely describes the interface pattern.

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