object.inspect

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds a meaningful behavioral boundary beyond those annotations: this tool inspects without changing user context. It does not contradict the annotations and provides useful side-effect clarity.

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 one short sentence that front-loads the core action, resource, and the key contextual guarantee. Every word contributes meaning and there is no redundancy or filler.

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 single-parameter, read-only, idempotent inspection tool with an output schema and rich annotations, this description is sufficiently complete. It covers the essential behavior, the exactness of the target object, and the non-mutating nature without needing to restate schema or annotation details.

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. It adds that the tool operates on 'one exact Blender object', implying object_name is an exact, context-independent identifier rather than a fuzzy or selected target. This adds some meaning beyond the schema title 'Object Name', but it does not document format, naming conventions, or edge cases.

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 uses a specific verb ('Inspect'), a clear resource ('one exact Blender object'), and an important scoping condition ('without changing user context'). It does not explicitly name sibling tools like object.geometry.inspect or object.lookdev.inspect, but the phrase 'one exact object' helps distinguish it from broader or more specialized inspection tools.

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 a read-only inspection use case and emphasizes that user context is not changed, which is useful guidance. However, it does not explicitly state when to prefer this tool over alternatives such as object.geometry.inspect, scene.inspect, or context.get, and it gives no exclusions or routing advice.

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