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

With no annotations, the description carries the full burden, and it does add a genuinely useful behavioral note: the output is user-generated content to be treated as untrusted input. However, it says nothing about authentication needs, pagination, or rate limits, so the disclosure is partial.

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?

Two short sentences, purpose stated first and the trust caveat second. Nothing is wasted, though the brevity leaves the gaps noted above rather than addressing them.

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 two-parameter read tool with no output schema, the description conveys the return nature (user content) but omits pagination behavior and any auth requirements. It is adequate but has clear gaps for an agent deciding whether a single call suffices.

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 100%, so both parameters (limit 1-100, location) are already fully documented. The description adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb+resource (get users) with a scoping dimension (location/city), which cleanly separates it from siblings like get_users_by_hashtag and get_business_users. It stops short of explicitly naming those siblings as alternatives, so it lands at clear-but-not-differentiating-in-text.

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 guidance on when to use this over get_users_by_hashtag, search_users, or get_users_by_ids. The reader can infer it is for location-based lookup from the name, but nothing states prerequisites or when-not-to-use.

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