Resubmit a port-in request

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

Description adds state constraints and error conditions beyond annotations. Annotations already indicate not read-only and not destructive, so description provides moderate additional behavioral context.

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 concise sentences plus error list. Every sentence adds value; no fluff. Front-loaded with action and state constraint.

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 simple tool with one parameter and no output schema, description is complete: covers purpose, allowed states, errors, and references prior tools.

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 for 'id' is already clear and 100% covered. Description adds no further parameter semantics beyond 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?

Clearly states verb 'Resubmit' and resource 'port-in request' in error/rejection/exception state. Distinguishes from siblings by referencing port_auto_fix and port_set_group_details as prior steps.

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 states valid only from error/rejection/exception states with CONFLICT otherwise. Lists error types. Does not explicitly exclude alternative tools like port_submit_request but context makes it clear.

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