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

With no annotations present, the description carries the full burden and covers it well: it declares read-only, warns that scores are not comparable across spec versions, and discloses provenance per input ('some are anchored on-chain, one is our own assertion and says so'). It also enumerates an explicit list of what the score does NOT claim, which is unusually strong caveat disclosure.

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?

Purpose and read-only status are front-loaded, and the specification of contents is dense but each clause earns its place. The opening sentence is long and run-on, which slightly hurts scannability, but nothing is redundant.

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 no output schema and no parameters, the description compensates by enumerating exactly what the returned spec contains: dimension weights and scope, per-dimension formulas, source endpoints, verifiability, composite formula, tier thresholds, and disclaimers. Nothing needed to call or interpret this zero-arg tool is missing.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is trivially 100% for an empty properties object.

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 states a specific resource (the Autonomy Score's published rules) and immediately scopes it against the sibling concept of the score itself ('so the number can be recomputed rather than believed'). An agent can distinguish this metadata/spec tool from get_autonomy without opening either schema.

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?

It gives explicit use cases — 'to check our score yourself, or to score an agent without us' — which tells the agent both a verification and an alternative-scoring path. It stops short of stating when NOT to use it (e.g. when you just want the score value, use get_autonomy), so it is clear but not fully routing.

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