reddit_user

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

With no annotations, the description carries the full burden. It only states it 'gets' data, implying a read operation, but fails to disclose authentication requirements (access_token is in schema but not described), rate limits, error behavior, or whether it returns all posts or paginated results.

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 concise at one sentence, but is too minimal and lacks front-loading of key constraints. It could be more structured to cover parameter usage and output briefly.

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?

Given 4 parameters, no output schema, and no annotations, this description is incomplete. It does not describe the return format (e.g., profile fields, post structure), pagination, or error responses, leaving an 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 description adds no meaning beyond the input schema. With only 25% schema coverage (only 'type' has a description), the description should compensate but does not explain 'access_token', 'username', 'limit', or the effect of different 'type' values.

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 'Get a Reddit user profile and posts' clearly states a specific verb and resource. It is distinguishable from sibling tools like reddit_post (single post) and reddit_search (search), but does not explicitly differentiate itself.

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 reddit_search or reddit_read. An agent would not know the appropriate context, such as retrieving a user's own posts vs. searching for content.

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