organization_external_reference_source_settings_delete

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

With no annotations, the description must fully convey behavioral traits. It only mentions 'Disable' and 'Requires a JSON request body', but does not disclose permanence, side effects, permissions, or reversibility. The phrase 'Disable' may conflict with the DELETE path, causing ambiguity.

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 a single sentence, concise and front-loaded with the resource name. However, it is under-specified and fails to earn its place by omitting critical details, making it merely adequate.

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 deletion tool with one parameter and no output schema, the description should explain return values, error conditions, and confirmation requirements. It does not, leaving the agent without sufficient context for safe 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?

Schema coverage is 100% (parameter 'body' has description 'JSON request body'), but the description adds no extra meaning beyond the schema. Moreover, it states 'Requires a JSON request body' while the schema indicates the body is optional (default null, anyOf includes null), which is misleading.

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 states 'Disable instance of the object' with the HTTP method and path, clearly indicating a delete/disable operation. The verb 'Disable' could be interpreted differently than 'delete' but is still specific. It distinguishes from sibling insert and update tools through the action.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., update or insert). There is no mention of prerequisites, context, or when to avoid using the tool.

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