Get rate limits

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds real behavioral content beyond them: what each bucket covers, the 95MB threshold that separates 'big_uploads' from 'general', and that counters carry max/remaining/reset. It doesn't mention window lengths or whether limits are per-account or per-IP, which would have completed the picture.

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 paragraphs: purpose and bucket taxonomy first, then what the payload contains and when to call. Every sentence carries information (the 95MB threshold and the 429 trigger are both actionable), with no filler or repetition of the title.

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?

With no output schema, the description still tells the agent what comes back — three named limit buckets, each with maximum, remaining, and reset time — which is exactly what an agent needs to reason about backoff. For a zero-required-parameter read tool, nothing essential is missing.

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?

There is a single optional parameter, response_format, and the schema description already covers it at 100% with an enum and default. The description adds no meaning about the parameter beyond the schema, so the baseline 3 applies.

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 ("Show the account's current API rate limits") and then enumerates the three buckets returned ('general', 'big_uploads', 'zip'). No sibling tool touches rate limits, so an agent can distinguish this from the file/site CRUD siblings immediately.

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 states concrete triggering conditions: call before bulk operations or after a 429 error. That is clear usage context that maps well to the bulk siblings (nekoweb_upload_file, nekoweb_import_zip). It does not explicitly name those siblings or state a when-not case, so it stops just short of the top.

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