brain_telemetry_info

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

No annotations exist, so the description carries the full behavioral burden. It does signal that the data is 'Live' (freshness/real-time) and links a public page for verification, but it omits whether the call is read-only, whether data is cached or sampled, rate limits, and any auth requirements.

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?

Three short sentences, front-loaded with the resource, then the return payload, then a reference URL. Nothing is redundant or padded.

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 no output schema and no annotations, the description must fully describe the response, and while it lists four payload categories it does not convey structure, units, or freshness semantics for any of them (e.g., what a 'spike' is or how averages are bucketed). It is adequate to decide whether to call, but thin for interpreting results.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The schema is empty with additionalProperties=false, so no parameter confusion is possible.

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 states a clear resource ('Live emotional telemetry for AgentWorld agents') and enumerates the concrete payload: neurotransmitter averages, mood distribution, recently active agents, and brain event spikes. It is distinguishable from any sibling, though it never names a neighboring tool to contrast with.

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 or when-not-to-use guidance, and no alternatives are named. An agent must infer from the word 'telemetry' that this is a read-only observational call rather than something to invoke before another action.

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