Get Uptime Kuma Prometheus Metrics

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

Annotations already mark the operation read-only, idempotent, and non-destructive; the description adds genuine extra context by disclosing the auth requirement (API key or username/password) and the raw Prometheus exposition return format. No behavioral surprises are hidden.

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?

Every sentence earns its place: endpoint, auth, return format, use case, and parameter count. The most important facts are front-loaded and the whole description is compact.

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?

For a zero-parameter read-only fetch with no output schema, the description is complete: it names the endpoint, states the authentication needed, describes the return format, and gives a parsing use case. Nothing essential is missing.

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 tool has zero parameters and the schema properties are empty, so there is no parameter meaning to add. The explicit 'No params' statement reinforces the schema and leaves no ambiguity for the agent.

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 opens with a specific verb and resource: 'Fetch Prometheus metrics from /metrics'. This clearly distinguishes the tool from siblings like uptime_kuma_get_monitor or uptime_kuma_get_heartbeats, which target individual monitors or heartbeat history rather than the Prometheus exposition endpoint.

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?

'Useful for AI to parse monitor_status, monitor_response_time' gives concrete context for when to call this tool. It does not explicitly name alternatives or state when not to use it, but the use case is clear enough for routing.

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