Your access + meter

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

Annotations already carry readOnlyHint=true and idempotentHint=true, and the description adds meaningful behavior beyond them: it explains that the entitlement tier is 'checked fresh, never trusted from the token' and that a tool-call meter is included. This gives an agent useful expectations about safety and freshness without contradicting the annotations.

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 dense sentences with no filler. It front-loads the core status information and then gives a concrete diagnostic trigger. Every clause serves a purpose.

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-only diagnostic tool, the description covers the key output areas: token verification, entitlement tier, usage meter, and access escalation. The only minor ambiguity is the exact meaning of 'meter' (used calls vs. remaining allowance), but the overall picture is complete enough for an agent to call the tool appropriately.

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 no parameters, so the schema fully covers the input surface. The description therefore does not need to compensate for missing parameter documentation. This matches the baseline for zero-parameter tools.

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 clearly identifies this as a status/access tool: it reports whether the bearer token verified, the entitlement tier, today's tool-call meter, and how to gain full access. Although it lacks an explicit imperative verb like 'returns' or 'reports', the content is specific enough that an agent can determine the tool's purpose. It also implicitly stands apart from the sibling data tools such as latest_article and venue_concentration.

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 gives a concrete trigger: 'Call this first when a subscriber tool is missing from tools/list or a call is refused.' This is clear contextual guidance for when to use the tool. It does not name alternatives or list when not to use it, but for a diagnostic status tool this is a solid and actionable usage cue.

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