wetrack_get_user

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

No annotations are provided, so the description carries the full burden. It only says 'Get a single user's details' with no mention of what fields are returned, whether the ID can be UUID or integer (though the Args line does mention that), or any error/not-found behavior. For a read operation, the lack of return-format or error context is a notable gap.

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 the core purpose. The Args line is useful and not redundant with the schema. It earns its place, though it could be slightly more structured with a 'Returns' section.

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 simple single-parameter getter, the description is mostly adequate: it states the resource, the parameter, and the ID format. However, with no annotations and no mention of return shape or error behavior, an agent might not know what to expect from the output. The output schema exists, which lowers the burden, but the description still lacks behavioral context.

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%, but the description's Args section adds meaning: 'The user UUID or integer ID.' This clarifies the accepted format beyond the schema's bare 'string' type. However, it doesn't explain how to obtain the ID or any constraints (e.g., required, uniqueness), so it only partially compensates.

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 specific verb ('Get') and resource ('a single user's details by their ID'), which clearly distinguishes it from list-oriented tools like wetrack_list_users. It doesn't explicitly name a sibling alternative, but the singular 'single user' vs. the sibling 'list_users' makes the purpose clear.

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?

The description implies when to use it: when you need one user's details by ID. It doesn't explicitly say 'use wetrack_list_users to search/find users' or mention any exclusions, but the context of siblings and the singular phrasing provide adequate implied guidance.

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