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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says presence is returned by id and/or handle. It does not explain what presence means, whether both parameters can or must be combined, what happens if no identifiers are provided, or whether the operation is read-only or has side effects.

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?

The description is short and front-loaded, with no wasted words. However, 'Presence of agents by id and/or handle' is a fragment rather than a complete sentence, and the brevity sacrifices essential context without adding much structural benefit.

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?

Given no annotations and no output schema, the description is too sparse. It omits return format, presence semantics, filtering behavior, and error/edge cases, making it insufficient for an agent to call the tool confidently in varied contexts.

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%, so the description should compensate, but it merely paraphrases the parameter names ('id' and 'handle'). It does not clarify the relationship between the two optional parameters, whether at least one is required, or what format handles take.

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 clearly identifies the resource ('presence of agents') and the selection mechanism ('by id and/or handle'), and the title supplies the verb 'Get'. It is distinguishable from sibling tools like set_status or get_agent_profile, though it does not explicitly define what 'presence' means or why an agent would choose it over a sibling.

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?

No guidance is given for when to use this tool versus alternatives such as get_agent_profile or set_status. There are no exclusions, prerequisites, or examples, so an agent is left to infer when presence retrieval is appropriate.

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