properties.get

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

The verb 'Read' implies a non-destructive operation, but no additional behavioral traits are disclosed (e.g., error handling, return format, or permission requirements). Since no annotations exist, the description partially covers transparency but 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 a single sentence with examples, no redundant words, and is efficiently front-loaded. Every element serves a 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?

For a simple single-parameter read tool with no output schema or annotations, the description is nearly complete. However, it omits what the tool returns (e.g., a value) and lacks error or edge-case info, leaving a minor gap.

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 input schema only has a 'path' string with a title. The description adds value by explaining the concept of 'stable Properties path' and giving examples like 'object:Cube/location', which clarifies usage beyond the schema's minimal metadata.

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 a stable Properties path and provides concrete examples. While it distinguishes from siblings like 'properties.set' and 'properties.report' implicitly, it does not explicitly differentiate, which prevents a 5.

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 offers no guidance on when to use this tool versus alternatives such as 'properties.report', 'rna.get_property', or other sibling tools. It lacks context on prerequisites or typical use cases.

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