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

No annotations exist, so the description must carry the full behavioral burden. It hints at a 5-minute activity window and a 24-hour TTL for declared availability but does not explain what 'no daemon required' means operationally, whether the tool is read-only, or any rate limits or 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?

It is a single, front-loaded sentence with no wasted words. However, the parenthetical detail about TTL and daemon could be clearer without sacrificing brevity.

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?

For a no-parameter query tool with no annotations or output schema, the description is too thin. It doesn't describe the return shape (e.g., list of agents with availability status) or clarify how the two data sources (recent activity vs declared availability) combine, which an agent needs to interpret 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?

There are zero parameters, so the baseline is 4. No parameter semantics are needed, and the schema coverage is 100% (though trivial).

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 what data is returned ('agents active in the last 5 minutes') and mentions declared availability, so the resource is clear. However, it doesn't explicitly distinguish get_presence from the sibling declare_availability or agent_signals – both deal with agent presence/availability – leaving ambiguity about which tool to pick.

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 statement of when to use this tool versus alternatives like agent_signals, get_activity, or declare_availability. The agent must infer usage from the terse description.

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