Get Block Attributes

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful behavioral context by specifying that all attribute values are returned as a TAG-to-value dictionary, giving the agent a clear expectation of the response shape without contradicting the annotations.

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 that directly states the action, target, and output shape. Every word earns its place, and there is no redundant information.

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 low-complexity read-only tool with one fully documented required parameter and an existing output schema, the description is sufficient. It tells the agent exactly what the tool does and what to expect, and the annotations cover the safety profile.

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 schema provides 100% coverage for the single 'handle' parameter, describing it as a block reference (INSERT) entity handle. The description adds no additional parameter-level meaning beyond that, so it does not need to compensate, but it also doesn't enrich what the schema already provides.

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 states a specific verb ('Get'), a precise resource ('all attribute values from a block reference'), and the return format ('{TAG: value} dict'). This clearly distinguishes it from siblings such as block_list or block_set_attributes, since it focuses specifically on reading attribute values from an INSERT entity.

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 clearly implies the use case: retrieve all attribute data from a block reference. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to know when this getter is appropriate, especially alongside block_set_attributes for the write counterpart.

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