create_manual_activity

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

Annotations mark this as a non-read-only, open-world write, and the description adds genuinely valuable context beyond them: the required millisecond precision on startDatetime, the live HTTP 500 failure mode it caused, and read-back verification of converted values. It does not cover auth requirements or rate limits, but the failure-mode disclosure is substantive.

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 dense run-on sentence built from semicolons, bold markers, and backticks. It is not front-loaded; the most important fact for an agent (that this creates a manual activity) is absent from the opening and only inferable indirectly.

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 six-parameter mutation tool with no output schema and only hint-level annotations, the description omits purpose, sibling differentiation, typeKey semantics, and timeZone conventions. The format details it does include are helpful but insufficient to call the tool correctly on first attempt.

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 0% schema coverage the description must carry parameter meaning, and it partially does: it explains the km→m and min→s conversion for distanceKm/durationMin and gives a concrete millisecond format for startDatetime. However, typeKey, timeZone, and activityName are left completely unexplained, so half the required parameters remain opaque.

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 never states what the tool does in plain terms; it opens with unit-conversion implementation detail and only implies creation via 'before building the request body' and the name itself. It also fails to distinguish this tool from its obvious sibling create_manual_activity_from_json.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling create_manual_activity_from_json is never referenced, so an agent gets no signal on which of the two creation tools applies.

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