Add User

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

With no annotations, the description carries the full burden of behavioral disclosure, yet it does not say whether this overwrites an existing token, errors on duplicate users, needs elevated permissions, or has side effects. Only the mutation intent is conveyed by 'Register'.

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 front-loaded sentence with no filler, which is appropriate for a two-parameter tool. The brevity, however, comes at the cost of the omissions noted elsewhere.

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?

The output schema removes the need to explain returns, but for a mutation with no annotations and 0% parameter documentation, the description should at least cover prerequisites, duplicate/overwrite behavior, and the username parameter. Key call-correctness information is missing.

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%, so the description must compensate for two undocumented parameters. It partially covers oauth_token (Foursquare OAuth) but says nothing about the required username, its format, or whether it maps to an existing Foursquare identity.

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 ('Register') and resource ('a new user's Foursquare OAuth token'), so the agent can distinguish it from read-oriented siblings like get_user_details and list_users. It stops short of naming an alternative or noting how it relates to remove_user.

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 call this versus siblings, no mention that it is the counterpart to remove_user, and no prerequisites (valid OAuth token, whether the target username must pre-exist). Usage must be inferred from the name alone.

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