langfuse-mcp-java

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

Annotations declare destructiveHint:true and idempotentHint:false. The description adds domain context ('human review') but does not explain these behavioral traits or what happens on duplicate calls.

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?

Four short sentences with logical structure: purpose first, then parameter constraints. Efficient though slightly repetitive with schema content.

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?

Adequate for a 4-parameter creation tool with annotations present. Omits return value description (no output schema exists) and error conditions, but covers essential inputs.

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 enum values (SESSION/TRACE/OBSERVATION, PENDING/COMPLETED) already present in schema descriptions without adding semantic value or parameter relationships.

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 tool 'Adds an item to an annotation queue' with the specific context 'for human review', distinguishing it from sibling create_annotation_queue which creates the queue structure itself.

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?

While it mentions the domain context ('for human review'), there is no guidance on when to use this versus alternatives like update_annotation_queue_item, or workflow prerequisites.

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