agent_status

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

No annotations provided. Description implies a read-only operation ('Show') but does not disclose behavioral traits such as whether refresh triggers side effects, rate limits, or data retrieval costs. The mention of json_output shape is a minor behavioral note.

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 sentences with purpose first, then parameter hint. No redundancy. Efficient.

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?

Has output schema, so return values are covered. However, the description assumes domain knowledge (autonomous learning loops, state, backlog, RSS) without explanation. Given many sibling status tools, more context is needed for correct selection and interpretation.

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?

Schema description coverage is 0%. The description adds meaning only for 'json_output' (stable shape for menu-bar app), but ignores the 'refresh' parameter. This leaves one parameter completely unexplained.

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 shows 'autonomous learning loops' with specific attributes (state, backlog, last pass, RSS). The verb 'Show' and resource are specific, but it does not differentiate from similar status tools like 'live_status' or 'spawn_status'.

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 on when to use this tool vs. siblings. The only usage hint is about setting json_output, which is parameter-specific, not tool-selection guidance.

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