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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating it 'opens nothing by itself.' It adds useful context about the output (step-by-step screens, buttons, fields) and the follow-up browser workflow. It does not cover auth requirements or rate limits, but the core behavioral expectation is clear.

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 front-loaded with what the tool returns and how to use it, followed by API-plan context. It is reasonably concise at three sentences with no major redundancy. Phrases like 'from ChatGPT, Claude or any AI agent' are slightly promotional but do not undermine clarity.

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 zero-parameter guidance tool with annotations and no output schema, the description provides enough information to call it correctly. It explains that the tool returns instructions rather than performing the action, and it names the cotlet_browser_* tools for execution. It could be slightly more explicit about the exact return shape, but the essential context is present.

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 explain. The baseline for a zero-parameter tool is 4, and the description correctly does not invent parameters or confuse the agent about inputs.

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 states a specific action: returning step-by-step instructions for logging body stats in Trainerize. It clarifies that the tool itself does not open or change anything, distinguishing it from actual logging performed through the cotlet_browser_* tools. The name and title 'Log body stats' could momentarily imply a write operation, but the description corrects that impression.

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?

It gives a clear workflow: call this tool to get the Trainerize screens, buttons, and fields, then execute the steps with cotlet_browser_* tools. It also notes that Trainerize's official API is only available on certain paid plans, which helps an agent decide whether to prefer an API route. It does not explicitly state when not to use this tool, but the intended usage is easy to infer.

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