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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description goes beyond them with genuinely useful domain context: the baseWeights explanation ('a set's weight is the total, so plates loaded = weight - base') and the fact that some settings are phone-only and therefore absent from what this tool can affect.

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 field inventory is front-loaded and every clause carries content, including the parenthetical formula that prevents weight-entry errors. The single long sentence is dense but readable; the trailing 'Read-only.' is somewhat redundant with annotations but serves as a quick scoping cue.

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?

With no output schema, the description must convey what comes back, and it does so by listing the setting categories and flagging the phone-only items. Read-only semantics are covered by annotations, so the remaining description is proportionate to a simple zero-parameter read tool.

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 tool takes zero parameters, so there is no parameter semantics to convey; the baseline for a no-parameter tool applies. Nothing in the description is needed to disambiguate arguments.

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 names the resource (the person's settings) and enumerates the specific fields covered: weight unit, visible nutrients, workout-calorie credit, weight goal, and baseWeights for plate-loaded/Smith machines. The 'Read-only.' tag and the note about what only the person can change on the phone signal this is the read counterpart to a mutation tool, though the sibling trainrec_change_settings is never named.

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?

Usage is only implied: 'Read-only' plus the mention of what can only be changed on the phone suggests this is for inspection rather than editing, but the description never states 'use this to read settings' or points to trainrec_change_settings for modification. An agent can infer the split but must do the work itself.

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