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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond it: no indication of what 'drag' is computed from, whether measurements are stored, thresholds for instability, or latency/rate expectations. For a measurement tool whose value hinges on interpretation, this is thin.

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?

A single front-loaded sentence with no redundant or padding clauses. It is efficient, though the density of undefined internal terminology ('execution drag', 'Behavioral OS ecosystem') costs some 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?

With an output schema present, the description need not explain return values, and the input schema is fully annotated, so the structural burden is low. However, nothing explains what the metric means or how to act on it, leaving a gap for a tool whose whole purpose is interpretive measurement.

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 each of latencyMs, promptLength and responseLength documented inline including units and minimums. The description does not reference any parameter or explain how prompt/response lengths combine into the reported metrics, so it adds no meaning beyond the schema; baseline 3 applies.

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?

Uses a specific verb ('Measures') followed by the concrete quantities being measured (operational latency, response length, execution drag), which maps reasonably to the three required inputs. It does not distinguish itself from siblings like systemores_analyze_trace_telemetry or systemores_evaluate_drift, and phrases like 'execution drag parameters' and 'cognitive throughput stability' are undefined jargon.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when an alternative such as evaluate_drift or analyze_trace_telemetry would be preferable. The only contextual hook is 'within the Behavioral OS ecosystem', which does not tell an agent when to select this tool.

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