regdata_california_sos_business

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

With no annotations, the description carries full burden. It discloses that the tool is a scraper (read-only), requires no API key, and returns specific entity data. It does not mention rate limits or data freshness, but the scraping behavior and result fields are transparent.

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 four sentences that front-load the tool's purpose and key features. It is clear but could be slightly more concise by merging some clauses. Overall, it is well-structured and informative.

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 complexity (scraper for a specific registry) and the absence of an output schema, the description adequately specifies input and output fields. It includes a recommendation for discoverability (call regdata_describe). However, it does not describe the result structure (e.g., array vs object) or pagination 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?

The input schema is minimal with only a maxItems parameter and additionalProperties true. The description compensates by specifying that the search input should be a flat object with fields like name, tax ID, or registration number, and advises using regdata_describe for exact field names. This provides essential guidance missing from 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?

The description clearly states the tool scrapes the California Secretary of State business registry, listing specific data fields (entity name, number, status, etc.). It provides a specific verb ('scrape') and resource, and the name distinguishes it from sibling tools focused on other registries.

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 instructs to search by name or entity number, notes that no API key is needed, and recommends calling regdata_describe first for exact fields. It does not explicitly list when to avoid this tool, but the name and context imply it's for California business registry lookups.

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