rb209_measurement_scotland_measurement_method

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

With no annotations provided, the description carries the full behavioral burden. It discloses that the tool is a POST endpoint that calculates a residue group, which implies a non-destructive computation. However, it does not mention response behavior, error conditions, or whether any data is persisted.

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 a single sentence with no wasted words. It front-loads the endpoint, HTTP method, and core purpose, making it immediately scannable and easy to parse.

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?

There is no output schema, so the description should explain what the tool returns, but it only says it 'calculates residue group'. It also omits preconditions, units of the result, and behavior when optional parameters are omitted, leaving important context missing for reliable invocation.

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 100%, with both 'smnDepth' and 'measuredSmn' clearly documented in the schema. The tool description adds no parameter-level detail beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 verb 'calculate', the resource 'residue group', and the scope 'using SMN measurement values in Scotland'. It also provides the explicit HTTP method and endpoint path, making the tool's function unambiguous and distinct from sibling measurement tools.

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?

The phrase 'in Scotland' implies this endpoint is for Scottish SMN measurement calculations, giving the agent some regional context. However, it does not explicitly state when to prefer this tool over alternatives like rb209_measurement_method or rb209_measurement_smn_conversion_method, nor does it mention any exclusions.

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