tenki_list_exposed_ports

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, fully covering the safety and idempotency profile. The description adds no further behavioral context beyond restating the action—it does not mention response format, prerequisites like an active sandbox, or any edge behavior. Since annotations carry the safety burden, a score of 3 is appropriate.

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 sentence of seven words, with no filler. The purpose is front-loaded and immediately clear, making it highly efficient for an agent to parse.

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 read-only listing tool, the description states the action, and the required parameter is fully documented in the schema. While there is no output schema, the description 'List the ports' implies the return type. The only minor gap is the lack of explicit return format, but this is not critical for a list operation.

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 input schema provides a descriptive comment for session_id, including its purpose and origin. The tool description itself adds no parameter-specific details. With 100% schema coverage, the baseline of 3 is correct because the schema does the heavy lifting.

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 uses the specific verb 'List' and the resource 'ports currently exposed from a sandbox', clearly distinguishing this tool from siblings like tenki_expose_port and tenki_unexpose_port. An agent can immediately understand what is being listed and for which entity.

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 description does not provide explicit guidance on when to use this tool or mention any alternative tools. The usage is implied by the verb and resource, but there is no 'use this when...' or 'instead of...' statement, leaving the agent to infer the appropriate context on its own.

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