get_search_budget

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

With no annotations provided, the description bears most of the burden for behavioral disclosure. It exposes useful non-obvious context such as a potential Spotify search ban and cache size, but it does not explicitly state that the tool is read-only or whether calling it consumes search quota. That is not a contradiction, but a behavioral 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 tightly-worded sentences: the first lists the exact data exposed and the second states perfectly useful timing. No filler words or redundant detail.

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 zero-parameter status check, the description tells the agent what data will be available and when to call it. It does not specify exact value formats or the meaning of 'cache size' or 'ban active,' but the context is sufficient to make an informed use decision.

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 and the schema has full coverage. There is no parameter-level meaning for the description to add, so the baseline of 4 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?

Description clearly defines the tool's resource: remaining search calls, cache size, and search ban status for today. It communicates the information returned, and it is naturally distinct from siblings such as get_api_limits or search. A slightly more explicit verb like 'returns' or 'reports' would make the purpose even stronger.

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?

'Check before bulk searching' gives a direct, actionable usage context. It does not mention when NOT to use this tool, nor explicitly differentiate from get_api_limits, but the usage cue is clear.

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