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

With no annotations, the description carries the full behavioral burden. It discloses an auth requirement (both monitorId and a one-time monitorToken), but leaves key traits unexplained: whether calling it consumes the 'one-time' token, whether it is strictly read-only, what 'health' counters mean, and any rate limits or failure modes. For a credentialed endpoint with zero annotation coverage, this is a substantive 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?

Two short sentences with no waste, and the credential requirement is stated up front alongside the purpose. Slightly terse given how much is left unspecified, but nothing is bloated or buried.

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?

No annotations, no output schema, and 0% parameter documentation mean the description is the only source of behavioral detail. It covers purpose and auth but omits token-consumption semantics, return shape hints, and error behavior, so an agent could call it but could not predict the consequences.

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 description coverage is 0% across three parameters, so the description must compensate. It only glosses monitorId and monitorToken (and adds the notable 'one-time' qualifier for the token), while the optional operationId is left entirely unexplained in both schema and description.

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 gives a specific verb and resource: 'retrieve health and usage counters for a private push monitor'. It is clearly a read of monitor telemetry, which is distinguishable from the create/revoke/history siblings in intent, though it never names or contrasts them explicitly.

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?

Usage is only implied by the phrase 'health and usage counters' plus the prerequisite 'requires its monitor ID and one-time monitor token'. There is no statement of when to choose this over monitor_history, nor any exclusion or precondition beyond the credential requirement.

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