nc_get_companies_by_sector

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

No annotations are provided, so the description carries the burden. It states 'Get all companies' which may mislead an agent into expecting unlimited results, whereas the schema includes a default limit of 50. It also does not mention the commune filter or any pagination behavior. While the description is honest about the general action, it omits notable behavioral nuances.

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 sentence, front-loaded with the primary action and scope. It contains no filler and is exactly as concise as needed.

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?

The description is adequate for a simple retrieval tool, but the phrase 'all companies' conflicts with the limit parameter, potentially causing incorrect expectations. It also does not mention the commune filter, though that is covered by the schema. Given the low complexity, it is mostly complete but has a notable gap regarding the limit behavior.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds only minor context for sector_code (identifying it as APE/NAF) and does not clarify limit or commune beyond what the schema provides. This meets the baseline but does not elevate it.

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 (Get) and resource (all companies in a specific activity sector), and distinguishes it from siblings like nc_search_companies and nc_get_company by focusing on the sector filter. It is specific and unambiguous.

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 for retrieving companies by sector but does not explicitly mention when to prefer this over nc_search_companies or other tools, nor does it provide exclusions. The context is clear enough for a simple use case, but there is no explicit guidance on alternatives.

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