Check MyChart Session

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable behavioral context by stating it 'Runs headless' and disclosing the exact return fields. This goes beyond the structured metadata to inform the agent about the tool's execution mode and output shape.

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 two sentences long, front-loads the core purpose, and packs essential usage and return information without any fluff. Every sentence earns its place.

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 the tool has no parameters and no output schema, the description fully covers the necessary context: what is checked, the return structure, and the conditional action to take. It leaves no critical gaps for a status-check tool.

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?

With zero parameters, the baseline is 4. The description doesn't need to explain parameter semantics, but it adds clarity by describing what the tool evaluates and returns, which is sufficient for a no-input status check.

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 checks both MyChart provider configuration and browser session login status, with a specific verb and resource. It distinguishes itself from siblings by focusing on the session status and explicitly referencing the mychart_login alternative when loggedIn is false.

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 description provides explicit usage guidance: 'safe to call any time' indicates when to use it, and 'If loggedIn is false, run mychart_login' gives a direct alternative action. This clearly orients the agent on when to invoke this tool versus the login tool.

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