pin_registration_guide

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

No annotations are provided, so the description carries the full burden. It only says 'DEMO', hinting at limited functionality, but does not disclose whether the tool is read-only, what it returns, or any side effects. This lack of detail leaves the agent guessing about the tool's 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 very short and front-loaded, with each sentence (purpose and demo flag) contributing value. It is concise, though perhaps an example of under-specification rather than tight writing.

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 has an output schema and one parameter, the description is incomplete. It does not explain how applicant_type influences the guide, what the output format or content is, or provide any disclaimers beyond 'DEMO'.

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 one parameter, applicant_type, with 0% description coverage. The description does not mention it at all, adding no meaning beyond the bare name and default. The agent cannot infer valid values or how it affects the guide.

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 it is a guide for registering for a KRA PIN, using a specific verb and resource. It is distinct from sibling tools like paye_calculator and vat_guide, which serve different purposes.

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 usage context is clear: it is for PIN registration guidance. However, it does not explicitly mention when to use this over sibling guides like vat_guide or tax_incentives_guide, so there are no exclusions or alternatives.

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