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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful access-control context ('owned or explicitly shared'), which tells the agent results are permission-scoped, but it omits return format, pagination, and any rate/refresh notes.

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 front-loaded sentence with no filler; the scope constraint appears before the list of returned data. It is efficient, though 'evidence mode' and 'heartbeat receipt regularity' are jargon that could be clearer.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. However, for a read tool surrounded by many near-synonym siblings, the absence of any disambiguation or usage context leaves the definition only minimally complete.

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% and there are two parameters, yet the description explains neither agent_id nor api_key semantics. With no schema documentation and no description-level compensation, the agent gets no guidance on what identifiers are valid or how api_key affects access.

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?

States a specific verb (Read) and specific resources (registry status, evidence mode, heartbeat receipt regularity) with a scope qualifier ('owned or explicitly shared'). It is clear what the tool returns, but it never names or contrasts with the many similar siblings (agent_health_status, agent_presence_history), leaving differentiation to inference.

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 when-to-use guidance, no exclusions, and no mention of prerequisites or alternatives. The agent must infer from the name alone when this is preferable to siblings like agent_health_status. The access-scope phrase hints at authorization but not at selection criteria.

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