get_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. It does disclose a useful behavioral nuance: property names come from a cached Roblox API dump when available. However, it does not mention output format, error behavior, or any other side effects beyond implying a read-only 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?

The description is two sentences long, with no wasted words. It front-loads the core purpose and includes the important cache caveat in a concise second sentence.

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 tool is simple with one parameter and no output schema, but the description is minimal. It tells what the tool does but does not describe the return structure or edge cases. While not a complex tool, a bit more detail about the output format would make it more 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?

Schema description coverage is 0%, so the description must compensate for the lack of parameter information. It mentions 'by ref,' but this merely echoes the parameter name 'ref' without explaining what a ref is, how to obtain it, or its expected format. This is insufficient given the parameter is the sole input.

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 tool's function: 'Read the properties of an instance by ref.' The verb 'Read' is specific, and 'properties of an instance' defines the resource. It distinguishes itself from sibling tools like get_children (reads children) and get_by_path (gets by path).

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 when to use the tool (when you have a ref and need properties), but it does not explicitly mention alternatives or exclusion criteria. No guidance is given on when not to use it or which sibling might be preferred in certain situations.

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