mmar_get_attribute_instances_for_class_instance

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

With no annotations, the description carries the disclosure burden. It indicates a read operation via 'Get' and implies a list of instances as the return, but it does not explicitly state read-only behavior, authentication requirements, or any side effects. This is adequate but not rich.

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, front-loaded sentence with no wasted words. It includes a helpful parenthetical clarification and is appropriately sized for the tool's simplicity.

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 get-by-parent tool with one parameter and no output schema, the description and schema are sufficient. It clarifies the key concept (class instance = element) but does not elaborate on return format or relationships to other tools, which is acceptable for this complexity level.

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% with the single parameter 'class_instance_uuid' described as 'The UUID of the ClassInstance'. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 the action ('Get'), the resource ('all attribute instances'), and the scope ('for a specific class instance'). This distinguishes it from sibling tools like mmar_get_attribute_instance (singular) and mmar_get_attribute_instances_for_relationclass_instance (different target).

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 description implies the tool is used to retrieve attribute instances associated with a class instance, with the parenthetical '(element)' clarifying the context. It does not explicitly mention exclusions or alternatives, but the sibling tool names make the different scopes evident, so the context is clear.

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