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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by stating that the tool returns a classification (supportive/neutral/headwind), which is not derivable from structured fields alone.

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 sentences deliver a scannable list of contents and a note on the returned classification. Every word earns its place, and the key scope phrase 'Inflation pillar indicators' is front-loaded.

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 zero-parameter, read-only retrieval tool with an output schema, the description covers the input context and return behavior sufficiently. It does not explain classification semantics or data vintage/caveats, but the output schema likely covers return structure and the annotations cover safety.

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?

The tool has zero parameters, so the schema provides no parameter semantics to cover. The description meaningfully fills the void by enumerating exactly which indicators are included, which is the relevant information for invoking this no-arg tool.

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 a specific verb-and-resource purpose: get inflation pillar indicators. It enumerates concrete sub-indicators (CPI, PCE, breakevens, wage growth), distinguishing it from siblings like get_growth_indicators and get_financial_conditions.

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 when inflation data is needed and names the exact coverage, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. No exclusions or alternatives are named, so the guidance is clear but implicit.

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