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

Annotations already declare this a safe, closed read (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the bar is lower. The description still adds real value by disclosing the surface of data exposed — email, vault names, recent activity, current task — which helps an agent judge whether calling it is appropriate before doing so.

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?

A single dense sentence with zero filler; the scope ('One agent') is front-loaded ahead of the field list. The colon-and-list fragment is slightly list-like to parse but every item earns its place.

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 required parameter, no output schema, and annotations covering the safety profile, the main remaining obligation is telling the agent what comes back — which the description does exhaustively. Minor gaps: no note on behavior when an agent is idle/absent, and 'temper' is left undefined.

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%: agent_id is documented with a regex pattern and a concrete example, and the schema itself points to get_account for enumeration. The description adds no further parameter meaning, so the baseline of 3 applies.

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 names the specific resource and its scope ('One agent') and enumerates exactly what is retrieved: status, model, temper, address, email, current activity, next wake-up, latest line, vault names, recent activity. That distinguishes it from catalog-style siblings, though the verb is implied by the name/title rather than stated ('get' / 'Check on').

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?

There is no explicit when-to-use guidance and no mention of alternatives such as get_account (which lists agents), read_agent_files, or talk_to_agent. Usage is only inferable from the title 'Check on an agent' and the field inventory; nothing tells the agent when this tool is the wrong choice.

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