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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to state whether the tool is read-only, what side effects occur, authentication needs, or expected behaviors. A bare definition of the data returned is insufficient.

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 is appropriately concise for a parameterless tool, but it could be improved by front-loading the verb and stating the action explicitly 'Get the measurement protocols...'.

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 no output schema and no annotations, so the description must explain what the tool returns. It only defines the concept of protocols without stating that the tool returns a list of them. For a simple retrieval tool, the description is incomplete.

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 has zero parameters and schema coverage is 100% trivially. The description adds no parameter information because none is needed. Baseline for 0-param tools is 4, and the description meets that standard without deficiency.

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 defines what measurement protocols are ('public metric definitions a construct is judged against') but does not explicitly state that the tool retrieves or lists them. The verb 'get' is implicit, but the description reads as a noun phrase definition rather than a clear action. It provides some context but lacks specificity about the tool's function, and does not distinguish from siblings like 'get_measurement' or 'get_observatory'.

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 description offers no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. It simply defines the concept without any contextual direction.

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