fmod_entity_isAbstract

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

The description claims the value is 'constant', implying read-only, but the input schema includes a parameter 'value' for assignment. This inconsistency is misleading and undermines transparency. Additionally, no behavioral traits (e.g., permissions, side effects) are disclosed, and there are no annotations to fall back on.

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, clear sentence with a bracketed note. It is extremely concise and to the point, with no filler content.

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 simple boolean property tool with two parameters, the description covers the basic purpose but omits important context about read/write behavior and does not clarify the contradiction between 'constant' and the writable schema. Without annotations or output schema, this gap leaves 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 schema already documents both parameters. The description adds no extra semantic meaning beyond what the schema provides, meeting the baseline for this dimension.

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 identifies the tool as representing the 'isAbstract' property of an entity, distinguishing it from related boolean property tools like fmod_entity_isGlobal and fmod_entity_isSingleton. However, it does not explicitly state that it can both read and set the property, leading to slight ambiguity.

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 alternatives, such as other entity property tools or data retrieval methods. The description simply defines what the tool represents without contextual usage advice.

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