ghost_http_post

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only reveals that an HTTP POST is performed and that a {status, body} object is returned. It does not describe side effects, error behavior, redirect handling, authentication, or security implications of making arbitrary external requests, which is a significant transparency gap for a network tool.

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 extremely compact: two short sentences with no filler words. The core operation is front-loaded, and the return shape is stated efficiently. However, its brevity is partly a consequence of under-specification rather than deliberate compression of rich content, so it earns a 4 rather than a 5.

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 4 parameters, no output schema, and no annotations, this description is insufficiently complete. It omits how parameters map to the HTTP request, what the `status` and `body` values look like, and any defaults for `content_type` or encoding. The presence of many sibling tools adds pressure to provide routing context, which is absent.

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 coverage is 0%, and the description provides zero parameter-level information. It does not clarify how `body`, `headers`, `content_type`, or `url` are used, leaving the agent to guess whether the body should be JSON-encoded, how headers are formatted, or what content types are accepted. The description completely fails to compensate for the schema's lack of descriptions.

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 states a specific action ('HTTP POST') and the resource being acted on (an HTTP endpoint), and it clearly distinguishes itself from the sibling ghost_http_get by naming the HTTP method. However, it could be more explicit that it sends a request to the provided URL and that `url` is the target, so it stops just short of a 5.

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?

There is no guidance about when to use this tool versus alternatives such as ghost_http_get, nor any mention of typical use cases (e.g., submitting form data, calling an API) or exclusions. The verb 'POST' implies a use case but leaves all contextual decision-making to the agent.

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