informal_sector_registry

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

Annotations are absent, so the description carries the full burden. It discloses only that the tool can 'register or look up', but gives no details about side effects, required permissions, data persistence, or the implications of the 'DEMO' marker. This is insufficient for an agent to anticipate behavior.

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 that efficiently conveys the core purpose without unnecessary fluff. The 'DEMO' tag adds a small but relevant piece of context about its non-production nature. It is concise, though it sacrifices 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?

Despite having an output schema and four parameters, the description provides minimal context. It does not specify possible action values, required fields for registration vs lookup, or any constraints on inputs. The tool appears simple, but the description still leaves critical operational gaps.

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 schema has four parameters with 0% description coverage, and the tool description does not mention or explain any of them. It fails to clarify what 'action' should be (e.g., 'register' vs 'lookup') or how 'name', 'trade', and 'county' are used, leaving the agent without semantic guidance.

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 registers or looks up informal sector workers, with specific examples (jua kali, boda rider, domestic worker). This clearly distinguishes it from sibling tools like job_match, wage_benchmark, etc., which address different labor-market functions.

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 when dealing with informal sector workers (registering or looking them up) but does not explicitly specify when to use this tool over the siblings, nor does it provide any exclusions or alternative recommendations. Usage context is implied by the domain but lacks direct guidance.

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