delete_attribute

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only restates that the tool deletes an attribute; it does not mention irreversibility, side effects on related notes, permissions, or what happens when the attribute does not exist. For a delete tool, this is a significant transparency gap.

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 focused sentence with no filler. It front-loads the action and identifies the target resource and selection method efficiently.

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?

The description is adequate for a simple attribute deletion, and the schema covers parameters. However, with no annotations and no output schema, the description lacks important context such as whether the operation is permanent, whether it affects the note itself, or how it differs from delete_note behaviorally. This leaves the tool minimally viable but not fully 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?

Schema description coverage is 100%, so the schema already documents all parameters clearly. The description adds the parenthetical '(label or relation)' which echoes the attributeType enum, but does not provide additional semantic detail beyond the schema. Baseline 3 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?

The description clearly states the verb 'Delete', the resource ('attribute (label or relation)'), and the scope ('from a note by name'). It distinguishes this operation from sibling tools like delete_note by specifying the attribute-level target rather than a note-level target.

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 gives clear context: use this tool to remove a label or relation from a note by its name. It does not explicitly discuss alternatives or exclusions, but the resource type is specific enough to avoid confusion with note deletion or note creation.

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