get_ateco

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

Discloses that it returns sector name, risk classification, and required courses. No annotations provided, so description carries the full burden. It does not cover error behavior or authentication needs, but for a simple lookup it is adequate.

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?

Three sentences: input specification, output description, and usage hint. No unnecessary words, well-structured.

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 and lack of output schema, the description adequately covers what the user needs to know. No mention of geographic applicability (Italy), but it's implied.

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% for the single parameter, and the description repeats examples already present in the schema. Adds no new meaning 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?

Clearly states 'Get a single ATECO 2007 economic sector entry by code or slug', specifying the resource and action. Differentiates from sibling search_ateco by explicitly targeting single entry retrieval.

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?

Provides a clear usage hint: 'Use this when the user mentions an Italian business sector or activity.' Lacks explicit exclusion or alternative suggestion, but context implies search_ateco for multiple results.

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