langfuse-mcp-java

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

The description contradicts the annotations. Annotations declare 'readOnlyHint: false' and 'destructiveHint: true', implying a mutation or destructive operation, while the description frames this as a safe retrieval ('Returns items'). This inconsistency could cause dangerous misuse by the agent.

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 appropriately front-loaded with the primary purpose, followed by filter details and return structure documentation (valuable given no output schema exists). Minor redundancy exists in stating 'queueId is required' (already in schema required array).

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?

Without an output schema, documenting the return item fields (id, queueId, traceId, etc.) is necessary and helpful. However, the description omits critical behavioral context regarding the contentious 'destructive' and 'openWorld' hints, leaving the agent unprepared for side effects.

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?

With 100% schema description coverage, the baseline is 3. The description repeats the enum values (PENDING | COMPLETED) and 'omit' behavior already documented in the status parameter description, adding no new semantic depth. It redundantly notes 'queueId is required' which the schema already enforces.

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 states the specific action ('Returns') and resource ('items in a specific annotation queue'), distinguishing it from sibling 'get_annotation_queue' by pluralization and content detail. However, it fails to hint at the destructive/non-read-only nature implied by annotations, slightly obscuring the true purpose.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_annotation_queue_item' (singular) or 'list_annotation_queues'. It explains the status filter behavior but offers no strategic usage context or prerequisites for the agent.

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