langfuse-mcp-java

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

Annotations declare destructiveHint=true; description adds crucial human-readable confirmation ('irreversible') emphasizing permanent data loss. No contradictions with annotations. Could add context about whether deletion cascades to related resources or failure modes when openWorldHint applies (IDs don't exist).

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 efficient sentences with zero waste: purpose front-loaded, safety warning second, parameter requirements third. No filler words or tautologies.

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 complete for a destructive 2-parameter operation. Annotations cover safety profile (destructive, not read-only) and idempotency (false). No output schema exists, so return values need not be explained. Minor gap: could clarify behavior when item doesn't exist given openWorldHint=true.

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% with complete descriptions ('The annotation queue ID. Required.'). Description adds redundant requirement confirmation ('Both...are required') without adding semantic meaning, examples, or relationships between parameters not evident in 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?

Clear specific verb ('Removes') and resource ('item from an annotation queue'). Unambiguously distinguishes from sibling create_annotation_queue_item (creates), update_annotation_queue_item (modifies), and get_annotation_queue_item (retrieves).

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 critical safety warning ('irreversible') which guides usage caution, but lacks explicit when-to-use guidance versus alternatives (e.g., when to prefer delete over update_annotation_queue_item) and lacks prerequisite context (e.g., needing valid IDs from list operations).

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