langfuse-mcp-java

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

Explicitly claims 'Read-only' but annotations indicate destructiveHint: true and readOnlyHint: false. This is a direct contradiction that misrepresents the tool's safety profile and potential side effects.

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-sentence structure is appropriately brief, but dedicates one sentence to the incorrect 'Read-only' claim, wasting limited descriptive space on misleading information.

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 address the destructive nature implied by annotations, provides no output format details, and doesn't explain what constitutes a 'trace' in Langfuse or why fetching user traces might be destructive.

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?

Mentions 'pagination' providing context for page/limit parameters, but with 100% schema coverage already describing all three parameters, the description adds limited semantic value beyond the structured 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 it retrieves traces for a specific user with pagination, but the 'Read-only' claim contradicts the destructiveHint: true annotation, creating confusion about whether this is a query or destructive operation.

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 on when to use this versus siblings like fetch_traces or get_user_sessions, nor any warning about the destructive behavior indicated by annotations.

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