bloom_validate_model

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

With no annotations provided, the description carries the full burden, and it discloses almost nothing: not whether validation is a read-only check, whether it requires the model to be loaded/installed, what constitutes a pass/fail, or whether it can fail. An output schema exists, so return-value detail is partly excused, but the behavioral gaps are substantial.

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?

A single short sentence, front-loaded with the verb, with no filler. Its problem is under-specification rather than verbosity.

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 tool with no annotations and zero parameter documentation, the description should explain what validation entails and when it applies. The presence of an output schema excuses explaining return values, but the agent still lacks the context needed to call this confidently alongside bloom_evaluate_model.

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 single 'model' parameter has 0% schema description coverage, and the description adds no format information (model ID vs. display name vs. provider-qualified string) to compensate. It is only mildly self-evident from the parameter name.

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 verb (Validate) plus the resource (model suitability for Bloom evaluation), which is slightly more than a restatement of the name. However, it never says what 'suitability' means (existence, capability, threshold compatibility) and does not distinguish itself from the close sibling bloom_evaluate_model.

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 when-to-use guidance, no prerequisites, and no mention of when to prefer this over bloom_evaluate_model or the other bloom_* tools. The agent must infer the routing entirely from the name.

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