create-body-measurement

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

No annotations are provided, so the description carries the burden of explaining behavior. It discloses the key 409 conflict behavior and optional field semantics. It stops short of mentioning authentication, success response shape, or idempotency, but the core mutation behavior and conflict handling are transparent.

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 two sentences, front-loaded with the primary purpose, and includes the most important behavioral caveat. Every sentence earns its place; there is no extraneous detail.

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 tool with 18 parameters, no output schema, and no annotations, the description covers the essential creation semantics, optionality, and conflict behavior. The only meaningful gap is the lack of success response details, but the rich parameter schema offsets much of the complexity.

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 input schema provides 100% coverage, with every parameter having a clear description and unit. The description adds little beyond the schema: it repeats that fields are optional and emphasizes the date uniqueness constraint, which is already in the date parameter description. Baseline 3 is appropriate given the schema's strong coverage.

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 function: 'Create a body measurement entry for a given date.' The verb 'Create' and resource are specific, and it distinguishes itself from the sibling tool 'update-body-measurement' by explicitly noting the 409 conflict and suggesting the alternative.

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 explicit usage guidance: 'Returns 409 if an entry already exists for that date — use update-body-measurement instead.' This tells the agent when not to use this tool and names the correct alternative. It also clarifies that all measurement fields are optional, informing how to construct calls.

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