reddit_get_profile

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 does not disclose that this is a read-only operation, nor does it mention authentication requirements (though 'me' implies it), error handling for invalid usernames, rate limits, or any side effects. The description only states the action and output, offering minimal behavioral insight.

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 a single, front-loaded sentence that begins with the verb 'Retrieve' and resource, then lists concrete examples of the returned data. It contains no fluff or redundancy, making it highly concise and well-structured.

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 tool with one optional parameter and no output schema, the description adequately conveys what the tool does and the special 'me' case. It does not mention error cases or explicit authentication requirements, but the schema already handles the 'me' semantics. Given its simplicity, the description is fairly complete, though it could benefit from noting read-only nature or potential errors.

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 schema description covers 100% of the parameter, including the special values 'me' and omitted for own profile. The tool description adds no additional parameter semantics beyond what the schema already provides. With high schema coverage, the baseline of 3 applies, and the description does not elevate it.

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 states the action (retrieve profile information) and the resource (user profile), listing specific fields like display name, bio, karma breakdown, cake day, and social links. It distinguishes the ability to target a user or 'me', but does not explicitly differentiate from sibling reddit_browse_user, which could also provide user information. Thus it is clear but lacks sibling differentiation.

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 provides clear context on when to use the tool: for a user or current profile ('me'). It does not mention alternatives or explicitly state when not to use it, but the context is sufficient for basic usage. It lacks explicit exclusions or comparisons to siblings.

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