users_get_presence

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the basic action. It does not state whether the tool requires specific permissions, whether it returns current or cached status, or any side effects. Given the lack of annotations, the description should compensate but fails to do so.

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 very concise with a single sentence, but this conciseness comes at the cost of completeness. It is not overly verbose, but it fails to include essential details about parameters or usage, making it minimally adequate.

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?

The tool has an output schema, but the description does not provide any context about what the output contains. Given the simplicity of the tool (one parameter, no annotations), the description should at least clarify the return value or expected behavior. It does not, leaving the agent underinformed.

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 only parameter 'user' is a string with no description. Schema description coverage is 0%, and the description does not explain what value to provide (e.g., user ID, email, or username). This leaves the agent without enough information to correctly invoke the tool.

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 'Get user presence information', which is a clear verb+resource mapping. It distinguishes from siblings like users_info or users_list by specifying 'presence'. However, it lacks specifics about what presence entails (e.g., online/offline, last active), making it slightly less informative than it could be.

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 provided on when to use this tool versus alternatives such as users_info or users_list. There is no mention of context, prerequisites, or when not to use it. The description is too brief to guide an agent on appropriate usage.

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