reddit_rate_limit_status

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

Annotations already provide readOnlyHint, and the description adds meaningful context by clarifying that results are scoped to endpoints used this session and reflect Reddit's communicated budget. It also explains the roughly 100-requests-per-minute constraint, which helps the agent understand the check's purpose.

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 dense sentences front-load the tool's purpose and then immediately provide actionable usage guidance. Every clause adds value; there is no filler.

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 read-only, zero-parameter status tool, the description covers purpose, scope, and when to invoke it. Since there is no output schema, a more specific statement about the return shape would be a minor improvement, but it is not necessary for correct invocation.

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 are zero parameters and the input schema is empty, so the baseline is 4. The description's session and endpoint scoping is sufficient context for a parameterless call.

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 opens with 'Report what Reddit has said about your remaining budget on each endpoint used so far this session,' which is a specific verb plus a clear resource. It is distinctly different from sibling tools like reddit_auth_status or reddit_request.

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 explicit timing guidance: 'check here before a large paginated read rather than after a 429.' It does not explicitly name alternative tools or exclusion conditions, so it stops just short of full when/when-not coverage.

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