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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic action ('List webhooks') and a domain limitation, but omits critical details such as authentication requirements, rate limits, pagination behavior, or what happens when no webhooks exist. The tool is a read operation, but more context is needed.

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 long and front-loaded with the core purpose. It contains no redundant information and every phrase adds value. This is highly concise and well-structured.

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?

Despite having no output schema and 9 parameters, the description is very brief. It does not explain return values, filtering, sorting, pagination, or any other contextual details. The tool is relatively complex (pagination, multiple parameters) but the description provides minimal completeness, making it harder for an agent to use correctly.

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 has 9 parameters with only 33% having descriptions (query_json, path_params, detail_profile). The tool description does not add any additional meaning for the other 6 parameters (page, sort, limit, cursor, include, per_page). Given the low schema coverage, the description should compensate but does not, leaving agents uncertain about parameter usage.

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 'List webhooks' and specifies the domain as 'Personio HRIS webhook configurations for delivery monitoring.' It also explicitly notes that 'Recruiting-domain events are not available,' which helps distinguish it from other tools. The verb+resource combination is specific and unambiguous.

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 contextual clues about when to use the tool (for delivery monitoring of HRIS webhooks) and a limitation (recruiting events not available). However, it does not explicitly mention when not to use this tool versus alternatives like list_webhook_activity or redeliver_webhook_events, which would strengthen guidance.

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