check_rate_limits

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

No annotations are provided, so the description carries the burden. It names the two values returned (remaining quota, reset time), which is useful, and the operation is inherently side-effect-free, but it never states that it is read-only or that it consumes no quota itself. With an output schema present, return-format detail is not required, so this lands at an adequate 3.

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 core purpose is front-loaded in one sentence, and the Args block is compact and waste-free. Every clause carries information an agent needs to call the tool.

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 one-parameter, read-only diagnostic tool with an output schema covering the return values, the description supplies purpose and full parameter enumeration. What it lacks is timing guidance for when to invoke it relative to the sibling request tools, which would make it fully self-sufficient.

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 0% and the single parameter has no enum, so the description must compensate — and it does, enumerating all four valid endpoint categories with a parenthetical meaning for each and stating the default ('search'). This adds real meaning beyond the bare string property, though it omits error behavior for invalid values.

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?

States a specific verb+resource: checking remaining request quota and reset time for X API endpoints. The purpose is unambiguous and clearly distinct in kind from the data-fetching siblings, but the description never explicitly contrasts itself with search_recent_posts/get_post/search_full_archive_posts/get_post_counts, so it stops short of full sibling differentiation.

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 implied by the nature of a quota-inspection tool, but the description gives no explicit when-to-use guidance (e.g., 'call before issuing requests' or 'after a 429'), nor any when-not condition or named alternative. Context is inferable rather than stated.

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