server_start

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

No annotations are provided, so the description carries the full burden. It discloses a meaningful behavioral trait: the tool blocks until the server answers. It also discloses the dependency on generate_certs for SSL mode, adding useful operational context beyond a trivial 'start' statement.

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 compact and front-loaded with the primary purpose, followed by a concise Args block. Every sentence and clause adds value—there is no fluff or redundancy.

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 tool with one optional parameter and an output schema, the description is complete enough. It covers the core behavior, the parameter meaning, and a prerequisite. The output format is not explained, but the presence of an output schema makes that unnecessary.

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 schema only provides the parameter name and type, with 0% description coverage. The description's Args section fully explains ssl: it means 'Serve over HTTPS', requires generate_certs first, and is necessary for the Maltego desktop client and Graph Browser. This adds complete semantic meaning beyond the 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?

The description clearly states the action ('Start the local transform server') and even adds the readiness condition ('wait until it answers'). This distinguishes it from sibling tools like server_stop, server_restart, and server_status.

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 gives specific usage context for the ssl parameter: it requires generate_certs first, and both Maltego desktop client and Graph Browser require HTTPS. However, it does not explicitly state when to use server_start instead of server_restart or when not to use it.

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