Prepare: Log Weight (FatSecret)

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

The description calls this a 'Dry-run' which typically implies no side effects, while annotations state readOnlyHint=false, indicating writes may occur. This is a direct contradiction, earning a score of 1.

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 extremely concise—two sentences that front-load the core purpose and key constraints without wasted words. It is well-structured and easy to scan.

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 7 parameters, no output schema, and the existence of a commit workflow (siblings include commit_prepared_operation), the description is incomplete. It does not explain what 'prepare' returns, how it connects to a later commit, or the full parameter set, especially given the misleading dry-run annotation.

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 0%, so the description must compensate. It explains currentWeightKg (kg), firstTimeSetup (only on first weigh-in), and date (via backdate limit). However, it omits reason, comment, and does not clarify currentHeightCm or goalWeightKg beyond the minimal schema ranges, leaving several parameters underdefined.

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 it prepares logging current weight in kg, with specific constraints that distinguish it from other prepare_* siblings (height/goal-weight only on first weigh-in, backdate limit). The verb 'prepare' and resource 'logging your current weight' are concrete and specific.

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?

Provides context that this is a dry-run preparation step and gives explicit usage constraints: pass firstTimeSetup=true only on the first weigh-in, and cannot backdate more than 2 days. However, it does not explicitly contrast with commit tools or other prepare tools, so alternatives are not named.

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