attribute_get

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 merely states the operation without indicating whether it is read-only, what happens when the attribute does not exist, or any potential errors or side effects. This is minimal behavioral information for an unannotated tool.

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, succinct sentence with no redundant wording. It front-loads the core action and resource, making it immediately clear without any fluff.

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 with two well-documented parameters and no output schema, the description covers the basic operation. However, it omits any context about return behavior, error handling, or differentiation from similar tools, leaving some gaps in completeness given the lack of annotations.

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%, as both 'target' and 'attributeName' have descriptive text in the input schema. The tool description adds no additional parameter-level details, so the baseline score of 3 is appropriate given the schema's adequate documentation.

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 ('value of a specific attribute'), and the target ('on an Instance'). It inherently distinguishes itself from siblings like attribute_get_all (which retrieves all attributes) and attribute_set/attribute_delete (which modify attributes), satisfying the specificity requirement.

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 provides no guidance on when to use this tool versus alternatives such as property_get or attribute_get_all. It does not mention exclusions, prerequisites, or typical use cases, leaving the agent to infer usage solely from the name and schema.

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