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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive. The description adds no conflicting info and provides minor extra context (publication schedule, public domain source). It does not disclose any additional behavioral traits beyond annotations, which is acceptable given the safety profile already covered.

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?

The description is three sentences long, front-loaded with the core purpose (lamb cutout) and report ID. It efficiently lists return values and source without redundancy. Every sentence provides useful information, making it an exemplar of concise, structured documentation.

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 the simplicity of the tool (2 optional parameters, output schema present, annotations clear), the description covers the essential aspects: what data is returned, when it is published, and its provenance. The all_sections parameter behavior is left to the schema, which is sufficient. Slight room to explicitly mention the effect of all_sections, but schema covers it.

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% for both parameters (report_date and all_sections), so the schema already fully documents their semantics. The description does not add parameter-specific guidance, but since the schema is thorough, baseline 3 applies. No contradiction or missing compensation needed.

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 description states exactly what the tool does: returns national estimated lamb carcass cutout values, enumerating the specific components (gross, foresaddle, hindsaddle, net, byproducts). It explicitly names the report ID (LM_XL502) and clearly differentiates from sibling tools (e.g., lmpr.beef.boxed_cutout, lmpr.hog.slaughter_prices) by specifying 'lamb'.

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 description implies usage for lamb carcass cutout data and notes it is published daily on USDA business days, which informs availability. It does not explicitly state when to prefer this tool over alternatives, but the sibling tool naming (beef, hog, etc.) makes the context clear. No exclusions or alternative guidance is given, but the purpose clarity largely suffices.

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