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

With no annotations, the description carries the burden. It strongly implies a read-only side-effect-free operation by describing 'state' and 'composition', and adds the important behavioral consequence that paused status causes every staking/AMM/governance write to revert. It does not explicitly state 'read-only', but the language is sufficient for a simple zero-parameter getter.

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 and front-loaded: it first lists what the tool returns, then immediately explains why it matters. Every clause adds value and there is no wasted 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?

For a zero-parameter read tool, the description fully covers what the agent needs: it enumerates the output categories and explicitly ties the tool to pre-write safety checks. The absence of an output schema is adequately compensated by this detailed listing.

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 input schema has zero parameters, so the baseline is 4. The description adds no parameter details, but none are needed. It instead clarifies what the returned data covers, which is more relevant here.

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 names the exact resource (protocol safety status) and enumerates its components: CircuitBreaker state and NFTVetoCouncil composition. This clearly distinguishes it from sibling tools like get_protocol_registry and the write-building 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?

It explicitly states when to use this tool: 'Critical context BEFORE sending any write'. It explains the consequence of not checking (writes revert if paused), though it does not mention alternative tools or when not to use it.

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