list_industries

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

No annotations are provided, so the description carries the burden of disclosing behavior. It states the tool lists industries (a read operation) and supports pagination, implying no side effects. However, it does not mention authentication requirements, rate limits, or what happens when the workspace does not exist. The behavior is mostly transparent given the simplicity of the tool.

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 short sentence that conveys the core purpose and a key feature. It is front-loaded and avoids unnecessary words. For a simple list tool, this is appropriately sized; however, it could be slightly expanded with usage context without becoming verbose.

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 lack of an output schema, the description should clarify what is returned (e.g., list of industry objects with fields). It mentions pagination but does not explain default sorting or ordering. The schema covers parameters, but the description omits return format and any potential limitations, making it incomplete for a full understanding.

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%, so the baseline is 3. The description adds 'Supports pagination,' which relates to page and per_page parameters but does not add specifics beyond what the schema already provides (defaults, max). No additional semantic value is given for other parameters like q or workspace_id.

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 tool lists target industries for a workspace, which is a specific verb+resource pair. It is easily distinguishable from sibling tools like create_industry or update_industry. However, it lacks additional scope detail like 'list all' or filtering constraints that could further differentiate it from other list tools.

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, nor does it state when not to use it. It only mentions pagination support, which is a feature, not usage context. The high example provided explicit alternative tool names, which is missing here.

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