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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds value beyond annotations by specifying this is 'live' and detailing the returned data categories (stability, ESG, fees, oracle health, settlement readiness), which helps the agent predict the response shape.

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: the first states the core capability and deliverables, the second gives use cases. It is front-loaded with the key phrase 'Get live DPX performance analytics' and contains no redundant or vague wording.

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?

This is a zero-parameter, read-only overview tool with an output schema present. The description fully covers purpose, output contents, and intended use cases. No further context is necessary for an agent to select and invoke this tool correctly.

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 an empty input schema, so there are no parameter semantics to clarify. Per rubric, 0 parameters earns a baseline of 4. The description adds no parameter information because none is needed.

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 uses a specific verb and resource: 'Get live DPX performance analytics.' It clearly lists the returned components (stability score, ESG composite scores, fee breakdown, oracle health, settlement readiness) and distinguishes this aggregate overview from sibling tools like dpx.metrics or oracle.stability.

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 explicitly states intended use: 'Use for dashboards, reporting, and AI-driven monitoring of protocol health.' This provides clear context for when to invoke the tool. It does not mention alternatives or when not to use it, but for a zero-parameter overview tool this is acceptable.

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