bloom_get_history

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

No annotations provided, so description must indicate behavioral traits. It states 'Get...' implying a read operation, but does not confirm idempotency, side effects, or data freshness. The description adds no behavioral context beyond the obvious.

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?

Single sentence, no waste. However, it is overly terse; it could include more information without losing conciseness. Structure is flat but front-loaded.

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?

Given the low complexity and presence of an output schema, the description still fails to mention that output schema or any details about the returned data. It lacks completeness for an agent to understand the tool's exact function.

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?

Schema has 2 optional parameters (model, behavior) with 0% description coverage. The description does not explain what these parameters do, how they filter history, or their expected values. The agent must infer from names alone.

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 states verb+resource: 'Get Bloom evaluation history.' It is specific but does not differentiate from sibling tools like bloom_evaluate_model or bloom_get_thresholds, which also deal with Bloom evaluations.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, context, or when not to use it. The description provides no decision support for the agent.

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