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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered. The description adds only that it returns seed in kg, which is largely redundant with the output schema. No additional behavioral context (rate defaults, rounding, units caveats) is provided.

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?

Four short sentences, each carrying a distinct fact (what, context, inputs, output), and the core computation is front-loaded. The trailing list_bundles reference is the only element of marginal value.

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 simple two-parameter calculator with an output schema and full annotation coverage, the description supplies enough to call it correctly. The one real gap is disambiguation from calculate_seed_quantity, which matters given the very large sibling set.

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 100%, so the schema already documents area_m2 and rate_g_m2. The description restates the same parameter names and units without adding meaning, and does not mention the default rate of 30 g/m². Baseline 3 applies when the schema carries the load.

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 and resource ('Compute grass seed quantity (kg) for a lawn area') with units, which is more than a restatement of the name. However, it does not distinguish itself from the sibling calculate_seed_quantity, leaving the agent to infer which is the generic vs. lawn-specific tool.

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?

'Use for landscaping' is implied context but not an explicit when-to-use statement, and no condition or exclusion differentiates it from calculate_seed_quantity. The pointer to list_bundles is a cross-reference to bundles rather than guidance on selecting this tool.

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