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. However, it only says 'Get one webhook_subscription,' which implies a read operation, but does not mention permissions, error behavior, rate limits, or what happens if the subscription does not exist. This lack of detail falls short of transparent behavioral disclosure.

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, consisting of two brief sentences. It wastes no words and is easily scannable. The first sentence is the core purpose, and the second adds useful context about the types of webhook subscriptions. While the second sentence is a bit awkward, it is still efficient and earns its place.

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?

The tool has 5 parameters, including nested objects, and no output schema, so the description needs to provide more context about expected return values and potential error scenarios. It only offers a minimal get-one statement and subscription type list, leaving out crucial information for an agent to fully understand the tool's behavior and integration.

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 high at 80%, and the schema already provides descriptions for most parameters (id, query_json, path_params, detail_profile). The tool description adds no extra parameter semantics, so the baseline of 3 is appropriate. The only undocumented parameter, 'include,' is not clarified by the description either.

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 with a specific verb and resource: 'Get one webhook_subscription.' It also adds context by enumerating the types of webhook subscriptions (candidate, job, event, GDPR, requisition), which helps distinguish it from the sibling list_webhook_subscriptions by emphasizing a single-item fetch.

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 does not provide explicit guidance on when to use this tool versus alternatives. It implies a single-item fetch through the word 'one,' but does not mention list_webhook_subscriptions for fetching multiple, nor any conditions for when to prefer this tool. No exclusions or alternative tools are referenced.

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