fmod_get_property

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

With no annotations, the description carries the full burden. It describes a read operation but does not confirm safety, side effects, permissions, or any behavioral traits. Minimal disclosure beyond 'Read'.

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?

A single, focused sentence with no extraneous words. It is efficiently front-loaded with the core purpose.

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?

The description does not explain the return value (likely the property value) since there is no output schema. It covers the tool's scope adequately but lacks details on what the response contains, which is important for a read operation.

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?

The schema covers target with a sufficient description but property lacks description (50% coverage). The description adds meaning by stating that property includes dynamic, per-class managed properties (e.g., 'timeline'), which compensates for the schema gap.

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 it reads any property of an object, including dynamic ones not in static reference (e.g., 'timeline'). This distinguishes it from sibling tools like 'fmod_set_property' and 'fmod_entity_properties'. The verb 'Read' and resource 'property' are specific.

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 (e.g., 'fmod_entity_properties' for static properties, or 'fmod_ManagedObject_properties'). The description implies it is for dynamic properties but does not explicitly state when not to use it.

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