langfuse-mcp-java

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

**Annotation Contradiction**: Description explicitly states 'Read-only' but annotations declare 'readOnlyHint: false' and 'destructiveHint: true'. This is a critical safety inconsistency. Additionally, it does not explain why a 'get' operation is marked destructive, nor does it address pagination behavior or 'openWorldHint' implications.

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?

Extremely efficient four-line structure with zero waste: purpose statement, parameter constraints, return value specification, and safety hint. Each sentence delivers distinct information in minimal words.

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?

Adequately documents return fields to compensate for missing output schema, but the behavioral contradiction and lack of sibling differentiation create critical gaps. For a simple list operation with 100% schema coverage, this would suffice if not for the safety inconsistency.

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%, establishing baseline 3. Description adds explicit return field documentation (id, content, authorUserId, etc.) which compensates for missing output schema, and reinforces objectType enum constraints beyond the schema's basic description.

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 'List comments' with clear filtering criteria (objectType, objectId) and enumerates valid objectType values (TRACE | OBSERVATION). However, it fails to distinguish from sibling 'get_comment' (singular) which likely retrieves a single comment by ID.

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 explicit guidance on when to use this tool versus sibling 'get_comment' or 'create_comment'. The filtering constraints are implied by parameter documentation but lack contextual prerequisites (e.g., needing a valid trace/observation ID first).

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