issue_passport

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

Discloses that the server silently captures Tier 0 observed signals and computes a passport grade (0-3), adding value beyond no annotations. However, does not mention auth requirements, side effects, or reversibility.

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 sentences, front-loaded with purpose and outputs, followed by behavioral insight. No redundant or unnecessary text.

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?

Describes outputs but does not specify return format or structure (e.g., JSON fields). With no output schema and no annotations, this is a gap for a tool that produces complex output. Adequate but not fully complete.

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 covers all 5 parameters with descriptions (100% coverage). Description adds minimal extra meaning by mentioning 'optional values floor' which is already in schema. 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?

States verb 'issue' and specific resource 'complete agent passport' with components listed (keys, signed passport, attestation summary, optional values floor). Distinguishes from siblings by focusing on passport issuance, not present in sibling names.

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?

Explicitly says 'Use this to onboard any agent — no npm install required.' Provides clear usage context (onboarding) but does not mention when not to use or contrast with alternatives.

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