hosting_listJsDeployments

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

No annotations provided, so description carries full burden. Discloses paginated list retrieval, domain requirement, and optional state filtering. Does not detail auth or side effects, but for a read-only list tool this is sufficient.

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?

Three concise sentences with front-loaded purpose, a usage directive, and behavioral detail. No redundant information.

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?

Adequately describes tool behavior given 4 parameters and no output schema. Covers pagination, domain requirement, and state filter. Could mention return format omission but acceptable for a list tool.

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 coverage is 100%, baseline 3. Description adds meaning to 'states' by mentioning 'filtering by deployment states' and specifies domain is required, but otherwise does not enrich beyond schema specs.

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 it lists JavaScript/Node.js application deployments for status checking, with specific verb and resource. It distinguishes from sibling tools like hosting_listNodeJSBuildsV1 (builds) and hosting_deployJsApplication (deployment creation).

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 'Use this tool when customer asks for the status of the deployment,' providing clear context for invocation. Does not mention when not to use or compare to alternatives, but the use case is well-defined.

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