herdr_agent_get

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It says 'Get details' which suggests a read-only operation, but it does not explicitly state that it has no side effects, requires no special permissions, or what error conditions might occur. There is no disclosure of safety profile or any caveats beyond the basic purpose.

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 a single sentence that is front-loaded with the core action and includes a parenthetical list of returned details. It is concise with no filler or redundant information.

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?

With one parameter, no output schema, and no annotations, the description should hint at the return format. It does by listing 'state, pane id, workspace, agent session,' but it does not explain the structure (e.g., object, array) or any possible failure modes. It is adequate for a simple getter but could be more explicit about what the caller receives.

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 100%, and the 'target' parameter is well-described in the schema as accepting terminal IDs, agent names, labels, or pane IDs. The tool description itself adds no additional meaning beyond the schema, so it meets the baseline but does not elevate it.

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's purpose: 'Get details for a single agent' and lists specific types of details (state, pane id, workspace, agent session). This is a specific verb+resource that distinguishes it from list tools like herdr_agent_list, and the word 'single' disambiguates from batch operations.

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 implies usage for fetching a single agent's details, but does not explicitly mention alternatives or when not to use it. Sibling tools like herdr_agent_list and herdr_agent_read exist, but no routing guidance is provided. The 'single agent' wording gives some implied context, but there is no explicit when/when-not.

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