fitbit_operation

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful safety directive about not resubmitting uncertain writes, but says nothing about what state values are returned or how to interpret them.

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?

Two short sentences, front-loaded with the tool's purpose. The second sentence is closer to a policy caution than a description of the tool, but it is brief and adds real decision value.

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 one-parameter read tool with no output schema, the description is adequate but thin: it never describes the possible operation states an agent would act on, nor that the tool is the intended follow-up to fitbit_commit/preview writes. Annotations carry the safety burden, so this is a moderate gap rather than a critical one.

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?

There is a single operationId parameter with 0% schema description coverage; the schema only supplies a UUID format and pattern. The description's reference to an 'operation' gives indirect semantics for the ID, but it never explains where the operationId comes from (presumably a prior write) or what to do if it is unknown.

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?

States a specific verb and resource: 'Inspect the persisted state of a meal/water operation.' An agent can tell this is a status/state-read tool rather than a mutation. It does not, however, distinguish itself from the sibling fitbit_status, which an agent might reasonably confuse it with.

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?

'Never silently resubmit uncertain writes' implies the usage context: check this after a write whose outcome is unknown (e.g. a timeout). The trigger is implied rather than explicit, and no alternatives or when-not-to-use conditions are named.

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