erp_test_webhook

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

No annotations are provided, so the description carries full burden. It mentions sending a request to a test endpoint with headers and body, implying a read/write operation, but doesn't disclose critical behavioral traits: whether it's safe (e.g., read-only vs. destructive), authentication needs, rate limits, or response format. For a tool with no annotations, this is a significant gap in transparency.

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 concise and front-loaded, with two sentences that directly state the purpose and key usage detail. There's no unnecessary information, making it efficient, though it could benefit from slightly more structure for clarity.

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?

Given the tool's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, response handling, error cases, and differentiation from similar tools like 'erp_test_hook'. For a testing tool with potential side effects, this leaves significant gaps for an agent.

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 100%, so the schema already documents all parameters (endpoint, method, body, params). The description adds minimal value beyond the schema by mentioning headers and body usage, but doesn't provide additional semantics like format examples or constraints. Baseline 3 is appropriate as 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 clearly states the tool's purpose: 'Test amaçlı webhook URL'sine ERP API request'i gönderir' (Sends an ERP API request to a webhook URL for testing). It specifies the verb (sends request) and resource (webhook URL for ERP API testing). However, it doesn't explicitly differentiate from sibling 'erp_test_hook', which appears similar, leaving some ambiguity.

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 provides minimal usage guidance: it mentions using the same headers and body for testing endpoints, but offers no explicit when-to-use rules, no alternatives (e.g., vs. 'erp_test_hook'), and no prerequisites. This lack of context makes it unclear when an agent should choose this tool over others.

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