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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side-effect behavior. The description adds the return format (list of streaks with fields) but does not disclose other behavioral traits such as pagination, sorting, or potential data freshness. Given the annotations carry the safety burden, the description's additional context is adequate but not rich, so a 3 is appropriate.

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 description is exceptionally concise: two lines plus a returns block. It front-loads the core purpose, then specifies the output structure. Every sentence earns its place, and there is zero waste or repetition. The structure is clean and immediately scannable.

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 simple read-only tool with no parameters, no output schema, and safety annotations already in place, the description covers all necessary aspects: what it does, what it returns, and the definition of a streak. There is no missing information an agent would need to invoke it correctly. It is fully complete for its complexity level.

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 has zero parameters, so the description has nothing to add regarding parameter meaning. The rubric assigns a baseline of 4 for 0-parameter tools, and the description does not introduce any confusion or missing information. It correctly remains silent on parameters since there are none.

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 clearly states the tool's purpose: 'Get budget streak data: consecutive months on-budget per category.' It names a specific resource (budget streaks), defines the concept, and specifies granularity (per category). It also lists the return fields, making the tool's function unmistakable. Among many get_* siblings, this one is uniquely identified by its focus on streaks.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, conditions, or how it differs from related gamification tools like get_gamification_summary, get_points_and_level, or get_leaderboard. An agent would have to infer its usage from the name and description alone, which is insufficient for optimal tool selection.

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