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

There are no annotations, so the description carries the full burden. It mentions 'comprehensive list' but does not explain behavioral nuances such as whether parameters filter results, pagination, or the response format. The read-only nature is implied by 'Retrieve' but no deeper behavioral details are disclosed.

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 a single concise sentence that front-loads the action and resource. It is free of fluff, though the phrase 'with the FMP Industry Classification List API' is slightly redundant given the tool name, but not harmful.

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?

There is no output schema, so the description should explain the return structure. It only mentions SIC codes and industry titles as included fields, but does not clarify that the optional parameters allow filtering, nor does it describe the overall response format. For a simple list tool with optional filters, this is insufficient.

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 coverage is 100%, and the parameter descriptions ('SIC code', 'Industry title or partial title') already convey their meaning. The description repeats these concepts without adding new details like examples, formats, or filter behavior, so it provides no value beyond the schema.

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 clearly states the verb 'Retrieve' and the resource 'industry classifications', including SIC codes and industry titles. It is specific enough about the tool's purpose, though it does not explicitly distinguish this from siblings like getAvailableIndustries or searchIndustryClassification.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that sicCode and industryTitle parameters can be used for filtering, nor does it contrast with other industry-related tools. Usage context is only vaguely implied.

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