Get current user

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description does add one useful behavioral nuance beyond the structured fields: the return may be a member OR a system user, implying an authentication context and a variable entity type. It says nothing about auth failure behavior or what fields come back.

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?

A single sentence with no filler, front-loaded with the verb and the exact resource. Nothing could be removed without losing meaning.

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 zero-parameter read with readOnlyHint and openWorldHint already declared, the definition is nearly sufficient. The only mild gap is that no output schema exists and the description does not sketch the shape of the returned member/system-user object, though this is a minor omission for a simple identity lookup.

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 tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The absence of arguments is itself consistent with a 'get current identity' operation, which the description implies.

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 and resource: 'Get the authenticated Reddit Ads member or system user,' which tells an agent this returns the identity of whoever is currently logged in. It is distinguishable from peers like get_business or get_ad, though it never explicitly contrasts itself with the adjacent reddit_ads_auth_status or reddit_ads_get_profile tools.

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 when-to-use guidance, no mention of prerequisites (e.g., must be logged in), and no routing to alternatives such as reddit_ads_auth_status for a lighter-weight auth check or reddit_ads_get_profile for profile data. Usage is only implied by the tool name.

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