langfuse-mcp-java

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

Description frames operation as safe retrieval ('Returns...'), but annotations declare destructiveHint=true. No explanation of what gets destroyed (archived? deleted? marked as consumed?) or why a 'get' operation is destructive.

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?

Three sentences. Return field listing is justified given lack of output schema. Minor redundancy stating parameter requirement that schema already enforces.

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?

Lists return fields adequately for missing output schema, but critically omits explanation of destructive behavior indicated by annotations. Does not clarify relationship between queue and items.

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 has 100% coverage with queueId described. Description redundantly states 'queueId is required' but adds no semantic context (format, UUID vs integer, where to obtain it).

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 (Returns) and resource (annotation queue) with scope (single by ID). Distinguishes from list_annotation_queues (plural) and get_annotation_queue_item (items vs queue container).

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 list_annotation_queues or create_annotation_queue. No mention of prerequisites or workflow context.

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