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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the shape of the returned data, which is genuinely useful, but says nothing about freshness/caching semantics of 'live', whether it is a global vs per-agent scope, auth requirements, or rate limits.

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 compact sentences plus a reference link, front-loaded with the resource and followed by the returned fields. No filler or restated boilerplate.

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 the enumerated return fields are a bonus rather than a necessity, and the parameterless schema means nothing else must be explained. The only real gaps are scope (population-wide vs per-entity), freshness guarantees, and access requirements.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals a parameterless global snapshot rather than implying any filtering input.

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 resource and verb — 'Live emotional telemetry for AgentWorld agents' — then enumerates the concrete payload (neurotransmitter averages, mood distribution, recently active agents with self-beliefs, brain event spikes). An agent knows exactly what this returns. It does not name or contrast any sibling (e.g. activity_feed, get_agent_trust_pulse), so it stops short of a 5.

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?

Usage is only implied by the word 'Live' and by the public-page link — an agent can infer this is a read-only current-state snapshot. There is no explicit when-to-use, when-not-to-use, or alternative named among the many sibling info tools.

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