clear_runtime_tokens

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

The description implies a destructive action (clearing memory) but does not elaborate on side effects, such as whether it invalidates the current session, requires re-authentication, or is safe to call multiple times. With no annotations available, more context would be beneficial.

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 tool is described in a single, precise sentence that is front-loaded with the action. Every word is necessary, and there is no redundancy.

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 that the tool has no parameters and the action is simple, the description is mostly complete. However, it lacks information about return values (though output schema exists) and potential failure modes, which could be helpful.

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?

There are no parameters, and the schema coverage is 100% (trivially). The description correctly implies no arguments are needed, so it adds value by confirming the tool's simplicity.

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 'Clear' and resource 'in-memory Salesforce and Data Cloud runtime tokens', making the purpose immediately clear. It distinguishes itself from sibling tools like refresh_oauth_token and start_oauth_token_flow, which deal with token lifecycle differently.

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 like refresh_oauth_token or start_oauth_token_flow. The description does not mention prerequisites, context, or exclusions, leaving the agent without decision support.

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