fmod_entity_properties

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

The description only mentions returning data, but the optional 'value' parameter implies potential write behavior (setting a property). This side effect is not disclosed. Without annotations, the description fails to convey the full behavioral scope.

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 repeated twice, with a cryptic tag at the end. It is not concise and contains redundancy.

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?

No output schema, and the description only vaguely mentions 'property description objects' without specifying their structure. The tool's dual nature (read/write) is not explained, leaving the agent underinformed.

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%, so the parameter descriptions exist, but the description adds no meaning about how 'value' interacts with the returned array. The relationship between reading properties and assigning a value is unclear.

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 it returns an array of property description objects, but the input schema includes a 'value' parameter for assigning a new value, which is unexplained. The purpose is ambiguous: is it read-only or read-write? The duplicate sentence adds no value.

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 on when to use this tool versus siblings like fmod_get_property or fmod_set_property. The description does not differentiate the tool's role.

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