langfuse-mcp-java

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

The description explicitly claims 'Read-only' which directly contradicts the annotations (readOnlyHint: false, destructiveHint: true). This is a serious inconsistency that could lead to unsafe agent behavior. The description fails to disclose what gets destroyed or why openWorldHint is true.

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 brief and front-loaded, but the 'Read-only' sentence is not only unhelpful but dangerously misleading given the destructive annotation. Every sentence should earn its place; the second sentence fails this criteria.

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?

Given the destructiveHint annotation and lack of output schema, the description should explain what gets destroyed/modified and what the tool returns. It addresses neither, leaving significant behavioral gaps uncovered.

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?

The mention of 'pagination' adds semantic context for the 'page' and 'limit' parameters beyond the schema's basic descriptions. With 100% schema coverage, the schema carries the primary descriptive burden, and the description provides minimal additional parameter-specific guidance.

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 states the core action ('List items in a dataset') and scope ('with pagination'), which is clear. However, the 'Read-only' claim contradicts the annotations (destructiveHint: true), undermining the accuracy of the purpose description.

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 provided on when to use this versus sibling tools like 'get_dataset_item' (single item retrieval) or 'list_datasets' (listing datasets themselves). No mention of prerequisites or when-not-to-use.

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