filter_ocel_attribute

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

Annotations are absent, so the description carries the full burden. It discloses that the tool dispatches to underlying PM4Py functions based on level and that retain controls inclusion/exclusion. This is adequate for a filter operation, though it does not mention if a new OCEL is returned or if the original is modified.

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 very concise with three sentences, no redundant information. It front-loads the purpose and adds detail in subsequent sentences. Every sentence adds value.

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?

Given the tool has 5 parameters (3 required) and an output schema exists, the description covers the core filtering behavior and key parameters. However, it leaves ocel_id and attribute unexplained, which is a minor gap. Overall, it is sufficiently complete for typical use.

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 0%, so the description must compensate. It explains level and retain parameters, but ocel_id and attribute are not described despite being required. The description mentions attribute and values in the purpose clause, which provides some context, but not enough for full parameter understanding.

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 'Filter an OCEL by event or object attribute values' which specifies the action and resource. It also explains the two levels and retain parameter, effectively distinguishing from sibling tools like filter_ocel_time_range or filter_ocel_object_types.

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 provides guidance on using level parameter to choose between event and object filtering and explains retain mapping to positive. However, it does not explicitly state when to use this tool versus other filter tools, such as filter_ocel_time_range, missing exclusion criteria.

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