classify_calibration_confidence

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

No annotations are provided, so the description carries the full behavioral burden. It usefully claims deterministic behavior and a Pro-tier requirement, but says nothing about what is classified, the output shape, error behavior, or the nested 'parsed_fields' contract, leaving the agent under-informed for a classification tool.

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?

Only the first sentence is functional; the following three sentences are marketing/upsell text (feature list, 'Requires Kiln Pro', upgrade URL) that does not earn its place in a tool definition. The result is front-loaded but then padded with irrelevant content.

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 a nested-object parameter, zero schema coverage, no output schema, and no annotations, the description should explain the 'parsed_fields' input and expected classification result. It instead spends most of its length on pricing, leaving the definition materially incomplete for correct invocation.

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 description coverage is 0% with two parameters (one required 'tool_name', one nested 'parsed_fields' object). The description adds no information about either parameter, so the agent must infer their meaning and structure entirely from bare property names.

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 opening sentence states a specific verb and resource ('deterministically classify ... calibration confidence'), which is more than a tautology. However, it does not distinguish this tool from calibration siblings such as assess_calibration_status, get_calibration_freshness, or apply_calibration_recommendations, and the purpose is diluted by three sentences of pricing copy.

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?

There is no guidance on when to use this tool versus the many calibration-related siblings. The only conditional statement ('Requires Kiln Pro') is a licensing prerequisite, not a usage or alternative-selection rule.

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