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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it falls short. 'Dual enforcement' strongly implies the tool performs some enforcing/mutating action, yet nothing states what enforcement does, whether it writes state, has side effects, or requires particular permissions. For an unannotated tool, this ambiguity is a meaningful gap.

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 short and front-loads the core purpose in the first sentence, which is good. But the second sentence, 'Bottom-up residual dynamics + dual enforcement,' is cryptic shorthand that doesn't earn its place — it introduces unexplained jargon instead of clarifying behavior. Concise in length but not in communicative efficiency.

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 tool that triggers a 'cycle' with enforcement behavior, and with no output schema and no annotations, the description should explain what running a cycle produces and what side effects it has. It does neither. The reliance on unexplained doctrine terminology makes the definition incomplete for an agent deciding whether and how to invoke it.

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 coverage is 100% and both parameters have descriptions, so the baseline is 3. The description adds marginal connective value by tying ticks to the 'Doctrine of 3 ticks' concept, and the rider_token schema entry already explains how to obtain the JWT. No real syntax or formatting detail is added beyond the schema, so a 3 is appropriate.

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 a specific verb and resource ('Run Smart Frame awareness cycles'), which distinguishes it from sibling cddg_* tools like cddg_bind_contract or cddg_query_plane on the surface. However, the qualifying jargon — 'Doctrine of 3 ticks,' 'Bottom-up residual dynamics + dual enforcement' — is unexplained and opaque, so an agent cannot truly grasp what the cycle does. It clears the tautology bar but leaves the core semantics fuzzy.

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 guidance on when to run this tool versus its cddg siblings (step, inject_swarm, query_plane, residual_summary). 'Doctrine of 3 ticks by default' hints at a convention but doesn't explain context or selection criteria. No exclusions, prerequisites, or alternatives are given, leaving the agent to guess when this is the right call.

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