get_oauth_session

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

No annotations are provided, so the description carries full responsibility. It clarifies that the session is simulated and lists the returned artifacts, which is useful. But it does not disclose what happens for an unknown or expired session_id, whether any state is modified, or whether a prior setup step is required. 'Inspect' implies read-only, but details are thin.

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. The verb comes first, followed by the object and the key contents, making it easy to scan and understand.

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 one-parameter tool with no output schema, the description does a good job of indicating what the return will contain (code, tokens, profile, expiry). It does not explain error behavior for missing sessions, but that is a minor gap given how low-complexity this tool is.

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% and the description never explains session_id. Although the parameter name and title are somewhat self-evident, the description fails to add format, example, or context for the session identifier. With low coverage, the description needed to compensate but did not.

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 tool's purpose with a specific verb ('Inspect') and resource ('simulated OAuth session'), and it enumerates what the session contains: code, tokens, returned profile, and expiry. This naturally distinguishes it from sibling simulation/setup tools like set_oauth_fake_profile or list_apps.

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 verb 'Inspect' implies the tool should be used when an agent wants to examine a simulated OAuth session, and there is no obvious alternative getter among the siblings. However, the description does not explicitly state preconditions, such as needing to set an OAuth fake profile first, nor does it call out alternatives or exclusions.

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