delete_ingress_source

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

Discloses that both the source and its delivery log are deleted, and that the endpoint immediately returns 404. No annotations exist, so description carries full burden; it adds useful behavioral context beyond a simple delete.

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?

Two sentences, one for action and constraints, one for behavioral note. No redundant or unnecessary words.

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 tool with one parameter and no output schema, the description covers action, side effect, endpoint behavior, and access restrictions. Complete for agent invocation.

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 single parameter source_id is fully described in the schema with 'Ingress source ID to delete'. No additional meaning is added by the description, and schema coverage is 100%, so baseline score 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?

Description clearly states 'Delete an inbound connector source and its delivery log by ID' with specific resource and scope. Distinguishes from siblings like delete_webhook or delete_automation.

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?

Explicitly includes 'admin only' and 'Hosted API only', providing clear context on when to use. Does not state exclusions or alternatives, but given the task domain, usage is well-defined.

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