Venice API Key Rate Limit Logs

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds material context they do not carry: experimental status, the ADMIN-key-only auth constraint, exclusion of inference keys, and the refusal of x402 wallet auth. It also bounds the result to the last 50 events, which is behaviorally important.

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?

Three tight sentences, front-loaded with what it returns, then the caveats. Nothing is redundant and no sentence could be dropped without losing an auth or scope constraint.

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 parameterless read endpoint with no output schema, the description covers the essentials: what is returned, how many records, and every auth prerequisite. An agent has everything needed to decide whether it can call it.

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 takes zero parameters, so there is no parameter semantics to explain; baseline is 4. The description's fixed 'last 50' scope correctly signals that no filtering or paging arguments exist.

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 precise verb+resource+scope: 'Get the last 50 exceeded rate-limit events for the account.' This is distinguishable from the sibling venice_api_key_rate_limits, which concerns current limits rather than a historical log of exceeded events.

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?

Gives clear operational context — experimental endpoint, ADMIN API key required, inference keys cannot call it, and no x402 wallet auth — which tells the agent whether it is even eligible to call it. It does not, however, explicitly name an alternative tool or a when-not-to-use condition relative to the rate-limits sibling.

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