SmartProspect: list sub-industries

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

The description provides substantial behavioral context beyond the annotations: it includes an explicit safety block (read-only, no credit consumption, no state changes, no email), the REST endpoint, and states it 'Does not reveal contacts and does not consume credits.' This goes well beyond the basic readOnlyHint and destructiveHint annotations.

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 four concise sentences that front-load the core purpose, then efficiently covers safety, endpoint, and key behavioral notes. Every sentence serves a clear function with no redundant or filler content.

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 the tool's simplicity, the presence of an output schema, and complete parameter documentation, the description is fully adequate. It covers purpose, safety, endpoint, and important limitations (reference data only, no credits), leaving no significant gaps for an agent to invoke it correctly.

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?

With 100% schema description coverage, every parameter already has detailed descriptions. The tool description doesn't add parameter-specific meaning but provides overall context about the data being listable. This meets the baseline of 3 for high schema coverage.

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?

Description clearly states the tool 'List[s] sub-industry values available as SmartProspect search filters' using a specific verb and resource. This distinguishes it from sibling list tools like list_industries and list_countries by focusing on sub-industries as reference 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 description implies usage context by stating these are 'available as SmartProspect search filters' and 'Reference data only,' which communicates that the tool is for retrieving filter options. It doesn't explicitly name alternatives or exclusions, but the purpose is clear enough within the sibling group.

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