langfuse-mcp-java

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

Critical contradiction: Description explicitly states 'Read-only' but annotations declare 'destructiveHint: true' and 'readOnlyHint: false'. This misrepresents the tool's safety profile and could lead to accidental data destruction. The description also fails to explain what gets destroyed despite the destructive hint.

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 short sentences with efficient structure. However, the 'Read-only' statement earns no credit since it contradicts annotations, reducing effective information density.

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 present, the description should explain the mutation behavior (what gets deleted/destroyed when fetching details?). Instead, it falsely claims read-only status. No output schema guidance provided.

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% (sessionId fully documented). Description implies the single-entity nature ('one session') but adds no semantic detail beyond the schema's 'Session ID' label. Baseline 3 appropriate given complete schema coverage.

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 (get full details) and scope (one session including traces). Clear verb-resource combo. However, fails to distinguish from sibling tools like 'fetch_sessions' or 'get_user_sessions' which likely overlap in functionality.

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 select this tool versus alternatives such as 'fetch_sessions' or 'get_user_sessions'. No prerequisites or conditions for use are mentioned.

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