langfuse_health

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

Discloses non-obvious constraints: required scope, governance by Arbiter policy, and cryptographic receipt. With no annotations, the description carries full burden and adds valuable behavioral context beyond a simple 'returns status'.

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 concise sentences: action, return value, and constraints. Front-loaded with the core purpose, no wasted words.

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?

Provides sufficient context for a simple health check: output includes ok status and org name, plus security details. No output schema exists, but the description covers the key return fields. Could mention typical response format (e.g., JSON) but not critical.

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?

No parameters exist, so the description correctly omits param details. The baseline of 4 is appropriate as schema_coverage is 100% and no param explanation is needed.

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?

Clearly states the tool checks Langfuse platform health and returns status and org name. Distinguishes from sibling health checks by naming the specific platform.

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 a precondition (required scope) but offers no guidance on when to use this tool versus other health check tools like probo_health or ragflow_health. Agent must infer usage from the tool name.

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