set_oauth_fake_profile

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

With no annotations, the description carries the behavioral burden. It does disclose a useful scoping detail: the profile is returned on the next login, suggesting a one-time or targeted effect. However, it does not mention whether the setting persists, whether existing sessions are affected, or what side effects or output to expect.

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 sentence with no wasted words. It front-loads the action, names the resource, lists the valid provider options, and specifies the timing—all in one compact clause.

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 description is sufficient for a simple setter with two parameters in a test context, but it assumes the agent understands the fake OAuth testing workflow. It omits return-value behavior, prerequisites such as registering an app or enabling fake OAuth, and whether the profile applies only once or repeatedly.

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. It partially does by naming valid provider values (google|github|facebook|x) and clarifying that 'profile' is the object returned by the fake provider. The inner shape of profile is left unspecified, though the schema's additionalProperties:true suggests arbitrary content is allowed.

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 uses a specific verb and resource: it 'Set[s] the profile' that a fake OAuth provider returns, and it enumerates the supported providers inline (google|github|facebook|x). It clearly identifies this as an OAuth test helper, though it does not explicitly contrast it with sibling simulation 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 guidance about when to use this tool versus alternatives like get_oauth_session or the simulate_* tools. The only contextual hint is 'on the next login,' which implies timing but does not state prerequisites, recommended call order, or situations where this tool should not be used.

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