fmod_entity_isSingleton

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

The description claims the property is 'constant', but the schema allows writing via the optional 'value' parameter. This contradiction is misleading. Additionally, no information about permissions, side effects, or return values is provided. Annotations are absent, so the description should fully disclose behavior.

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 with a tag, which is concise but lacks important details. It is front-loaded but insufficiently informative for an AI agent to use correctly.

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 no output schema and low complexity (2 params), the description is incomplete. It does not explain the behavior when setting the value (if writing is intended), nor does it describe what the tool returns on read. Missing critical behavioral context.

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 baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions. It does not elaborate on when to use the 'value' parameter or clarify the 'className' usage.

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 is a constant boolean value indicating singleton status, but does not explicitly state the tool's action (read/write). The schema includes an optional 'value' parameter for writing, creating ambiguity. It is clear that it relates to entity singleton property but lacks a verb.

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 sibling tools like fmod_entity_isAbstract or fmod_entity_isGlobal. The description does not differentiate it from other entity property tools.

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