mass_get_property

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the batch read intent, but does not mention return format, behavior when some instances lack the property, partial failures, or performance characteristics — important for a batch operation.

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, concise sentence that is immediately understandable and front-loaded with the action. No filler or repetition.

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 tool with 2 simple parameters and no annotations, the description is adequate for basic invocation but lacks critical context such as expected output (e.g., a map of path to property value) and how errors are handled. It covers the core purpose but leaves operational details unaddressed.

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% with clear descriptions for both paths and propertyName. The description adds a minor extra ('same property', 'multiple instances') but does not provide deeper semantic context beyond what the schema already states.

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 names a specific operation: 'Get the same property from multiple instances at once.' The verb 'get' plus the resource 'property from multiple instances' precisely distinguishes it from siblings like get_instance_properties (all properties of one instance) and mass_set_property (batch write).

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?

The phrase 'from multiple instances at once' implies a batch use case, but there is no explicit guidance on when to prefer this over alternatives like get_instance_properties or search_by_property, nor any exclusion criteria. The usage context is implied rather than stated.

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