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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral context worth having: each task may be selected at most once and the input is capped at 32 tasks. It does not state that the result is an exact optimum vs. approximation, nor anything about the returned structure.

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?

Two tight sentences, objective stated first, then the two governing constraints. No filler and nothing repeated from structured fields.

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 read-only solver with no output schema, the description never indicates what is returned (e.g., the chosen task set and total value), leaving the agent to guess the response shape. Objective and constraints are complete, but the result contract is missing.

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%, so the description must compensate, and it largely does: 'budget' is framed as integer minutes and 'items' as tasks with name/duration/value that can each be selected once, capped at 32. The nested task fields' exact semantics are left to the schema, which is acceptable given their self-evident 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?

States a specific verb (select) and resource (tasks) plus the exact objective: maximize total value within an integer-minute budget. This is a precise combinatorial optimization description that an agent can act on immediately, and it is clearly distinct from the unrelated siblings (chess, orbits, markets).

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 budget-maximization framing implies when to use it, but there is no explicit when-to-use/when-not statement and no named alternative. Since no sibling is a plausible substitute, the practical risk is low, but the guidance is only implied.

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