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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the output contains 'dated stock/price history' and 'authorized public supplier observations', which is useful context about the nature of the data, but it does not disclose rate limits, pagination, or data-source caveats beyond what annotations imply.

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 one compact sentence with no filler. It front-loads the action verb and the resource, immediately conveying both purpose and input constraint without wasted words.

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 one-parameter read-only lookup with no output schema, the description communicates the core return payload ('observations' and 'dated stock/price history') and the exact-match requirement. It does not describe the exact structure of returned records, but the low complexity and the coverage provided by annotations make this adequate. The only notable gap is the lack of guidance on how this relates to the similarly named 'aerospace_part_price_trend'.

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 input schema has no parameter descriptions (0% schema coverage), so the description must carry the semantic weight. It adds the key constraint that the part number must be 'exact', which is important for a lookup tool and not present in the schema's min/max length information. It does not provide example formats or explain what 'observations' means, but for a single simple parameter the added clarity is meaningful.

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 uses a specific verb ('Return') and names the resource ('authorized public supplier observations and dated stock/price history') tied to an exact part number. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tool 'aerospace_part_price_trend', which likely overlaps on price-history data.

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 phrase 'for an exact part number' implies the tool is for exact-match lookups rather than fuzzy or partial searches, giving some usage context. However, it does not mention when to prefer this tool over related aerospace siblings such as 'aerospace_part_price_trend' or 'aerospace_events', nor does it list any exclusions.

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