openpanel_decrement_property

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

With no annotations provided, the description carries full burden. It discloses the prerequisite constraint and numeric validation requirement, but lacks details on return values, error behavior if profile doesn't exist, atomicity, or authorization requirements.

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?

Three tightly structured sentences with zero waste. Front-loaded with the core action '[UNIFIED] Decrement...', followed immediately by critical prerequisites and constraints. Every word earns its place.

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?

Appropriately complete for a simple arithmetic operation, covering prerequisites and validation. Minor gaps remain regarding the 'site' parameter explanation and return value description (though no output schema exists to require this).

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 0%, requiring the description to compensate. It implicitly covers 'profile_id' (user profile), 'property_name' (numeric property), and 'value' (decrement amount), but fails to explain the 'site' parameter semantics or provide parameter-specific format guidance.

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 uses specific verb 'Decrement' with clear resource 'numeric property on a user profile'. The action clearly distinguishes from sibling 'openpanel_increment_property' through the directional verb, and scope is limited to existing user profiles.

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 states prerequisite ('Profile must exist first') and names the specific prerequisite tool ('use identify_user'). Also clarifies validation constraint ('Property must be numeric'), giving clear conditions for successful invocation.

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