objects_delete_object_record

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

Annotations already declare the tool as destructive and idempotent. The description adds no additional behavioral context such as permanence, side effects, or required permissions. It repeats the destructive nature without providing new information.

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 under-specified, consisting only of 'Delete Record'. While concise, it lacks substance and fails to provide useful information for agent decision-making.

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 destructive operation, the description omits any caution about irreversibility, expected outcomes, or error handling. With no output schema, it doesn't describe return values or success criteria, making the tool underspecified.

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 provides detailed descriptions for both parameters (id and schemaKey), covering 100% of the schema. The description adds nothing beyond what's already in the schema, so the baseline score of 3 applies.

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 'Delete Record' is a minimal restatement of the tool name. It does not specify which record type or how it differs from other delete tools in the sibling list, such as objects_delete_custom_object (though that one isn't present, but other deletes exist). It lacks specificity to guide an agent.

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 other delete tools or how to obtain the required parameters. The schema descriptions help for parameters, but the description offers no contextual advice.

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