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

Annotations already establish a safe, idempotent, closed-world read, so the bar is lower. The description goes further by disclosing the matching algorithm (best-for list plus inclusions), the budget filter, and the notable detail that the early-sign price is used while it applies — real behavioral context beyond structured fields.

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?

Front-loads the core action, then adds mechanism and trigger examples in tight sentences. The three quoted examples are somewhat redundant with each other but earn their place as disambiguation cues; overall it is appropriately sized.

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?

With no output schema, the description carries the return burden and does state that it explains why a package was chosen. For a deterministic recommender with fully documented params, the only meaningful omission is any explicit sibling comparison or mention of fallback when no package fits the budget.

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 coverage is 100% and each parameter already carries a detailed description, so the schema does the heavy lifting. The description reinforces that budget is applied against the early-sign price, but adds little about goals or context semantics beyond what the schema states.

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?

Opens with a specific verb+resource ("Recommends ... partnership package") scoped to ELC Conference 2027, and the deterministic matching behavior is stated explicitly. The example utterances make it easy to distinguish from catalog tools like list_packages or get_package.

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 example phrases ("we want to hire engineers in Prague", "which sponsorship level should we take") clearly signal the situation that should trigger this tool. However, it never names the obvious alternatives compare_packages or quote_partnership, nor says when not to use it, so the routing guidance is implicit rather than explicit.

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