list_webhooks

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

No annotations are provided, so the description must bear the full burden. It states the return type (dict with status, message, webhook list), but does not explicitly confirm it is read-only or mention rate limits, auth needs, or side effects. The name implies listing, but more specificity would improve 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 very concise, with a clear main purpose, prerequisites, and structured args/returns. Every sentence is necessary and front-loaded.

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?

For a simple list operation with one parameter and no annotations, the description covers the purpose, prerequisite, parameter, and return format adequately. It could mention the read-only nature explicitly, but overall it is complete.

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 only doc_id without description, but the tool description adds that it is the document ID and mentions the prerequisite list_documents to obtain it. This adds meaningful context beyond the bare schema.

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 lists webhooks for a Grist document. It distinguishes itself from sibling tools like create_webhook and delete_webhook by focusing on listing.

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 a prerequisite (list_documents to get doc_id), indicating when to use this tool. However, it does not explicitly discuss when not to use it or compare to alternatives like clear_webhook_queue.

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