epic_login

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

There are no annotations, so the description carries the behavioral disclosure burden. It mentions 'stored session,' implying a persistent state change, but does not explain side effects, authorization-code single-use behavior, session overwrite semantics, or error conditions. This is thin for an auth mutation tool.

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 efficient sentence with no filler. The key scoping information, including the source sibling, is front-loaded.

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 no annotations and no output schema, the description leaves important gaps: what the tool returns, possible failure modes (e.g., invalid or expired code), and what 'stored session' means for subsequent steps. For an essential auth step, this is incomplete.

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 adds meaning by specifying the parameter is an Epic authorizationCode obtained from epic_get_login_url, beyond the schema's bare string type. However, it omits format, expiration, or how the code should be passed, so compensation is partial.

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: 'Exchange an Epic authorizationCode ... for a stored session.' It clearly identifies the input source (epic_get_login_url) and the outcome, which lets an agent distinguish this from sibling tools like epic_auth_status or epic_get_login_url.

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 phrase 'from epic_get_login_url' explicitly places this tool after that step in the login flow, giving clear contextual usage. It does not spell out when-not-to-use or alternative conditions, but the intended sequence is evident.

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