get-webhook-subscription

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the conditional behavior ('if a subscription exists') and the return contents (URL and auth token). However, it does not specify what happens when no subscription exists (e.g., returns null, empty object, or 404) or any potential side effects, error conditions, or sensitivity of the auth token. This is adequate but has clear gaps for a no-annotation scenario.

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 two sentences, front-loaded with the main action ('Get the current webhook subscription'), followed by a concise explanation of the return value and condition. Every sentence earns its place with no redundant information or fluff.

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 has no parameters, no annotations, and no output schema, the description provides necessary context: what it does, the account scope, and what it returns conditionally. It mentions 'if a subscription exists', which implies handling of the absence case, though it could be more explicit about the no-subscription outcome. Overall, it is sufficiently complete for a simple getter 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?

The input schema is empty (0 parameters), and the description correctly does not attempt to describe parameters. According to the rubric, 0 parameters has a baseline of 4, and there is no additional semantic burden. The description focuses on the operation and return values, which is appropriate.

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: 'Get the current webhook subscription for this account.' It specifies the resource (webhook subscription) and its scope (this account), and differentiates from sibling tools like create-webhook-subscription and delete-webhook-subscription by focusing on retrieval. Additionally, it mentions what is returned (URL and auth token), further clarifying the purpose.

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 clear context: it is for retrieving the current webhook subscription and explicitly notes the conditional return ('if a subscription exists'). While it does not name alternatives or state when not to use it, the sibling tool list makes the distinction obvious (create/delete vs. get). This is clear context without explicit exclusions, aligning with a score of 4.

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