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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the description is not burdened with safety disclosure. It still adds real value beyond them: the data is bundled from GSA with no API call, and M&IE does not vary seasonally unlike lodging — both behavioral facts an agent could not infer from annotations or schema.

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-loaded with the resource and its contents, then the data-source note, then the seasonal caveat. The seasonal paragraph is short and earns its place, though the parenthetical detail in the first sentence is slightly dense.

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?

An output schema exists, so the field enumeration in the description is supplementary rather than required. With only one optional parameter, the definition is nearly complete, but the silent omission of any fiscal_year semantics is a genuine gap for a tool whose entire input is that parameter.

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% for the single fiscal_year parameter, so the description must carry that burden but never mentions fiscal_year at all. It does not say what happens when the parameter is omitted (which bundled years exist, whether it defaults to the current fiscal year), leaving the only input undocumented in both places.

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?

Names a specific resource — the M&IE tier breakdown table — and enumerates the fields it contains (breakfast, lunch, dinner, incidental, 75% first/last day), which makes the output unambiguous. It does not explicitly contrast itself with siblings like lookup_city_perdiem or estimate_travel_cost, so differentiation is implied rather than stated.

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?

Usage is only implied via 'for showing the meal component of a per diem estimate'. There is no explicit statement of when to call this versus lookup_city_perdiem or estimate_travel_cost, and no prerequisites or exclusions are given.

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