imladris_status

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

Fully discloses what it returns and does not return (no secrets, no liveness probe). No annotations exist, so description carries full burden; it does so comprehensively.

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?

Two concise sentences: first lists returned items, second adds constraints. No fluff. Front-loaded with key purpose.

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 tool with output schema (implied), description covers what the agent needs to know about the tool's input and output, despite not listing return values.

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, so baseline 4. Description adds no parameter info, but none 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 it returns resolved non-secret config (presets, provider roles, egress info, context-budget state) and explicitly excludes liveness probes and secrets. Differentiated from siblings: 'imladris' (presumably main) and 'imladris_clear_sessions' (session clearing).

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?

Implicitly indicates use for obtaining non-secret config; notes it performs no liveness probe (so not a health check). No explicit when-not or alternatives, but context is clear.

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