garmin_resume_session

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states that the tool loads a session from disk, uses a default path, and makes other tools authenticated. However, it does not describe side effects such as whether it overwrites the current in-memory session, validates session freshness, or what happens if the session file is missing or expired.

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 short sentences with no filler. The core action is front-loaded, and the usage context plus default path are stated efficiently. 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?

The tool is simple: one optional parameter, no annotations, and an output schema exists. The description covers the main purpose, when to use it, and the default path. It could be more complete by mentioning the fallback to garmin_login when no valid session is saved, but the description is adequate for a tool of this complexity.

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?

The schema provides only a string parameter with a default of empty string and 0% description coverage, so the description must compensate. It adds the meaningful detail that the default path is ~/.garth, which likely corresponds to session_path, but it does not explicitly describe the parameter's meaning or format. This is partial compensation for the schema gap.

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 action: resume a previously saved Garmin session from disk. It identifies the resource (saved session) and the tool's role in authenticating subsequent calls. It does not explicitly contrast itself with garmin_login, but the phrase 'previously saved session from disk' makes the distinction reasonably clear.

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 explicitly instructs to use this tool (or set GARTH_SESSION_PATH) before calling other tools, which gives clear operational context. It identifies an alternative setup method but does not explicitly describe when not to use it, such as when no saved session exists or when a fresh login is needed.

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