ps_send_webhook

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

With no annotations, the description carries the full burden, and it does disclose important behavior: the webhook URL comes from an environment variable, headers/body template come from the Periscope config, and template variables are substituted in both URL and body before sending. However, it omits failure behavior, what happens if the URL or config is missing, auth requirements, and whether the call blocks or retries.

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 short sentences that front-load the action and then the mechanics; the parameter list is dense but earns its place given 0% schema coverage. Minimal filler, though the second sentence packs a lot into one clause.

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?

An output schema exists, so return values need not be described. But for a side-effecting external notification with no annotations, the description should cover failure modes and the unresolved config_path/periscope_path parameters; it does enough to call the tool but not enough to predict its behavior.

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 0%, so the schema provides no parameter meaning, and the description compensates by naming most substitution variables (#{date}, #{language}, #{important_items}, #{all_items}, #{result}, #{summary}) and explaining that they are replaced in URL/body. It leaves config_path and periscope_path completely unexplained (and #{timestamp} has no matching parameter), so it only partially covers 8 undocumented params.

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?

States a specific verb+resource combination ("Send a webhook notification") and clarifies that it uses a configured URL, request_body template, and headers. It is unambiguous about what the tool does, though it does not differentiate itself from any sibling (no sibling handles webhooks, so the ambiguity risk is low).

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 explicit guidance on when to use this tool versus alternatives, no prerequisites stated as conditions, and no exclusions. The mention of config/env-var sourcing implies a setup requirement but never tells the agent under what circumstances to invoke it.

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