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

With no annotations, the description carries the full behavioral burden, and it does disclose the key trait: the call yields a plain not-available response with no data and no side effects. It does not specify error semantics, status codes, or whether the response shape differs from siblings, but the critical outcome is disclosed rather than hidden.

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 short sentences with no filler, and the unavailability is front-loaded in the first clause. The opening 'Not available.' is slightly ambiguous in isolation (it reads like a field value), but the second sentence resolves it immediately.

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 zero parameters, no output schema, and no annotations, the description covers everything an agent must know: the tool is a dead end and returns no data. The only meaningful omission is a pointer to a substitute source for manufacturing data.

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 takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No parameter documentation is needed or missing.

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 plainly that the SupplyMaven Manufacturing Index is not offered and that the tool returns a not-available response, which is a concrete and unambiguous statement of behavior. It distinguishes this tool from live-data siblings like manufacturing_output_indicator by making clear no data is produced. It is not a classic verb+resource purpose, but for a stub it communicates exactly what an agent needs.

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 text effectively implies 'do not rely on this tool' by declaring the index is unavailable, but it stops short of saying so explicitly or naming an alternative source such as manufacturing_output_indicator or get_freight_transportation_index. The implication is clear enough for an attentive agent, yet no when-to-use/when-not guidance is stated outright.

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