search_emission_sectors

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

With no annotations, the description carries the full burden. It discloses the returned fields and gives a meaningful example, but does not explain matching behavior such as case sensitivity, ordering, or how max_rows affects results.

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 very concise, with only three sentences, front-loaded with the core action, and includes a helpful example without unnecessary detail.

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 existence of an output schema and the simple read-only nature of the tool, the description covers the main purpose and return values well. It only lacks explicit mention of max_rows semantics and differentiation from describe_emission_sector.

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 0%, so the description must compensate. It clearly explains that query is a code prefix or name substring, but max_rows is left implicit except for the schema default of 50.

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 finds IPCC inventory sector codes by code prefix or name substring, with an example ('transport' -> 1.A.3). It specifies the return fields, distinguishing it from sibling tools like describe_emission_sector.

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 intended use is clear: search for sectors by prefix or name substring. However, there is no explicit guidance on when to use this tool versus describe_emission_sector or other siblings, and no exclusions are mentioned.

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