Create Manual Activity

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

Annotations already indicate destructiveHint=true and openWorldHint=true, so the description carries less burden, but it adds no behavioral context beyond those hints. It does not explain side effects, whether activities can be overwritten, authentication needs, or what happens after creation.

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, concise sentence with no unnecessary detail. It is front-loaded and easy to parse, though it mostly restates the title with only the small addition of 'manual activity entry in Garmin Connect.'

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 create-type tool with 7 parameters and no output schema, the description is minimally viable because the schema covers inputs and annotations flag mutability. However, it lacks information about return behavior, constraints, or integration context, making it incomplete for richer decision-making.

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 100%, and each parameter already has a description with units or format where appropriate. The tool description adds no additional parameter semantics, which is acceptable since the schema fully documents all fields.

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 says 'Create a manual activity entry in Garmin Connect,' using a specific verb and identifying the resource. It distinguishes itself from 'upload_activity' by specifying a manual entry, though it does not explicitly contrast with sibling tools.

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?

There is no guidance about when to use this tool instead of alternatives like 'create_workout' or 'upload_activity.' The word 'manual' implies hand-entered data, but no explicit usage context or exclusions are provided.

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