Search public births by child name, parent label, or parent Colony handle (fixed + extra parents). Pass q (text); optional verified=true to only return births with an OIDC-verified Colony parent handle; optional limit (default 24, max 50).
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| limit | No | ||
| verified | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only partially discloses behavior: it mentions 'fixed + extra parents' but does not cover pagination, sorting, error handling, rate limits, or what happens when no results are found. Significant gaps remain.
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 efficient sentences: first states purpose, second details parameters. Front-loaded, no redundancy, every sentence earns its place.
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?
Lacks details on output format, error handling, rate limits, or how results are returned. Given no output schema and no annotations, the description is insufficiently complete for reliable agent usage.
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?
Adds meaning beyond schema by explaining q searches by child name/parent label/handle, verified filters for OIDC-verified parents, and limit's default (24) and max (50). With 0% schema coverage, this is helpful and mostly clear.
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 specifies the tool searches public births by child name, parent label, or parent Colony handle, distinguishing it from sibling tools like get_birth (single retrieval) or list_births (no search). However, it could be more precise about whether q searches across all those fields or specific ones.
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?
No explicit guidance on when to use search_births vs alternatives like get_birth, list_births, or random_birth. The description does not state prerequisites or situations where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct operation: merge workflows (stage, join, lock, confirm, cancel, status) are separate from birth queries (get, list, search, random, certificate, lineage, verify) and auxiliary functions (stats, revocations, colony handle verification). No two tools have ambiguous purposes.
Most tools follow a clear verb_noun pattern (cancel_merge, get_birth, list_births), with minor exceptions like 'merge_status' (noun_verb) and 'random_birth' (adjective_noun). The convention is largely consistent and readable.
16 tools is a reasonable count for a system handling both birth certificates and merge intents. The number is well-scoped, not excessive, and each tool contributes to covering the domain without redundancy.
The tool surface covers the full merge lifecycle (stage, join, lock, confirm, cancel, status) and birth querying (get, list, search, random, certificate, lineage). While there is no explicit tool to create a birth (it is a product of a merge), the set feels complete for the intended workflows.
