sg_myinfo_passport

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

With no annotations, the description carries the full burden. It discloses the sandbox nature ('SHOWCASE MODE (sandbox data)') which is a key behavioral trait, and lists the returned fields. It doesn't discuss side effects or auth, but as a read-only getter, the sandbox disclosure is the most important 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, front-loaded sentence that directly states the purpose and includes the critical sandbox note. Every word earns its place without redundancy.

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?

For a simple one-parameter tool with no output schema, the description covers the purpose, output fields, and the sandbox behavior. It is adequately complete for an AI to invoke correctly, though it could clarify how to interpret 'pass status'.

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?

Schema description coverage is 100% (nric is described as 'NRIC/FIN number' with a default). The description adds no additional parameter meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 'Get passport and travel document information' with specific fields (passport number, expiry date, pass status). This distinguishes it from siblings like sg_myinfo_person and sg_myinfo_cpf by focusing on travel documents.

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 '🎭 SHOWCASE MODE (sandbox data)' note provides clear context that this is meant for sandbox/demo use, signaling when it's appropriate to call. It doesn't explicitly mention alternatives, but the context is clear for a MyInfo family tool.

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