business_registry_search

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

No annotations are provided, so the description bears the behavioral disclosure burden. 'Search' and 'Find' imply a read-only lookup, and the resource is clearly scoped to the Canadian federal business registry. However, it does not mention pagination, result limits, matching behavior, or federal-versus-provincial coverage limitations.

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?

Two short, purposeful sentences. The first front-loads the searchable resource, and the second enumerates the relevant filters without any unnecessary wording.

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 tool is a moderately simple search with an output schema, so return values are likely covered. The main gap is the meaning and formatting of the required 'q' parameter, plus expectations around 'limit'. The description is adequate for tool selection but not fully complete for reliable invocation without further inference.

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 does name useful filter dimensions: name, province, city, status, and industry act. Still, the required 'q' parameter is not explicitly defined, and 'limit' is not mentioned, leaving some ambiguity about how to construct queries.

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?

States a specific verb and resource: 'Search the Canadian federal business registry.' The second sentence adds the entity type and filter dimensions (name, province, city, status, industry act), which clearly distinguishes it from sibling property, permit, and zoning 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 makes clear this is for searching Canadian federal corporate/business records, and the sibling tools are all in different domains (property, permits, zoning). It does not explicitly state when not to use it, but the context is clear enough that an agent can select correctly.

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