log_exercise

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

There are no annotations, leaving the description to carry the full burden. It does not disclose any behavioral traits beyond the basic action, such as side effects, authorization requirements, or response behavior, which are important for a write operation.

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 very concise, one sentence that front-loads the core purpose. It wastes no words, although it is somewhat sparse, it remains appropriately structured for its brevity.

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?

The tool has 7 parameters and no output schema, yet the description provides no context about return values, required fields, or typical usage. This is insufficient for a logging tool with multiple parameters and no structured output to clarify behavior.

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 schema description coverage at 86%, the baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides, so it neither improves nor harms the semantic clarity.

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 the tool's purpose using the verb 'Registra' and resource 'atividade física', which is a specific action on a specific resource. It distinguishes from sibling tools like log_water and log_calories by focusing on physical activity.

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?

No usage guidance is provided. The description is a single sentence with no mention of when to use this tool versus alternatives, nor any exclusions or prerequisites.

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