iys_register

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

Discloses atomic batch behavior (one bad record fails entire request with 422), error codes for missing consent, and the mandatory nature. No annotations exist, so description carries full burden; it covers key behavioral traits well.

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 paragraphs, front-loaded with purpose and key details. Every sentence adds value, though the reference link could be integrated more tightly.

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 nested parameter structure and lack of output schema, the description covers the registry context, atomicity, error codes, and links to docs. Remains slightly incomplete on return behavior, but sufficient for the agent.

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 already provides descriptions for all fields, so baseline is 3. The description adds context about brandCode and the batch atomicity, but does not significantly extend meaning beyond 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 creates İYS consent records for the Turkish national registry, explains the legal mandate, and distinguishes it from related sibling tools like send_sms.

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?

Provides clear context for usage (submitting consent records), limitations (up to 5000 per request, atomic batch), and references to documentation. Lacks explicit mention of when not to use or alternatives like iys_check, but sufficiently guides the agent.

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