agentlens_agents

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

Each action is described (e.g., unpause clears paused state), and the tool's primary behaviors are disclosed. However, no annotations exist, and the description could further clarify that list/detail are read-only and unpause is a write operation.

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?

The description is concise with a clear structure: purpose, when-to-use, action list, and example. Every sentence adds value without redundancy.

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?

The description completely covers the tool's functionality given the 3 parameters and no output schema. It explains all actions and their outcomes adequately.

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 coverage is 100%, and the description adds context by explaining what each action does (e.g., 'list: List all agents with error rates'). This supplements the schema's parameter descriptions.

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 'List, inspect, and manage AgentLens agents' with specific actions (list, detail, unpause) differentiating it from sibling tools like agentlens_alerts or agentlens_analytics.

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?

The description explicitly provides 'When to use' guidance covering listing, inspecting details, and unpausing agents, though it does not explicitly mention when not to use or alternatives.

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