Clear port-out PIN

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

Contradicts annotations: description claims 'idempotent' while annotations set idempotentHint: false. Adds some context (MFA requirement, return code) but the contradiction undermines trust.

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?

Efficient two-sentence structure front-loading purpose, with critical details (idempotency, MFA, return code, error, sibling tools) in compact form. Deduction for contradictory statement.

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?

Covers return code and error case, links to related tools. Lacks details on idempotency behavior consistency and no output schema. Adequate for a simple tool but incomplete due to contradiction.

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?

Only one parameter (tn) with full schema coverage; description adds no additional meaning beyond the schema's format example. 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?

Clearly states the action ('clear'), the resource ('port-out PIN'), and context ('on a number you own'). Differentiates from siblings by mentioning the get and set counterparts.

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 prerequisites ('Requires step-up MFA'), success response ('Returns 204 No Content'), and a common error ('TN_NOT_OWNED'). Implicitly guides usage via reference to sibling tools, but lacks explicit when-to-use vs. alternatives.

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