fmod_ManagedObject_properties

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool 'provides access' and returns a map, implying read-only behavior, but does not explicitly state that it is non-destructive, has no side effects, or requires any specific permissions. The behavioral transparency is minimal.

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 concise with two sentences that directly state the purpose and return type. It is front-loaded with the key action. No unnecessary words. However, it could benefit from slightly more structure, such as a brief hint about the parameter format or return usage.

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 getter tool with one parameter and no output schema, the description provides the essential information: what it does and what it returns. However, it does not explain what a ManagedPropertyMap is or how to interpret its contents, which may be necessary for an agent to fully utilize the output. It is adequate but not complete.

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 coverage is 100% for the single 'target' parameter, with a clear description in the schema. The tool description does not add any additional meaning or constraints beyond what the schema already provides. Therefore, the baseline of 3 is appropriate—the description does not improve parameter understanding beyond the schema.

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 provides access to an object's properties and returns a ManagedPropertyMap. The verb 'access' and noun 'properties' make the purpose specific. Among sibling ManagedObject tools, it differentiates by referencing properties, but does not explicitly contrast with others like 'fmod_ManagedObject_document' or 'fmod_ManagedObject_dump'.

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 alternatives. The description does not mention prerequisites, exclusions, or usage context. An agent would have to infer from the tool name and sibling list that this is for reading properties, but no explicit 'when-to-use' or 'when-not-to-use' is provided.

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