get_object_info

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Get detailed information' without stating that it is read-only, what happens if the object does not exist, or any side effects. This is a significant gap for a tool that relies on the description for transparency.

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 concise: one clear sentence plus a short parameter explanation. It is front-loaded with the primary purpose, and every sentence adds value without unnecessary 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?

Given the tool is a simple getter with an output schema available, the description adequately covers the only parameter and the core action. It does not mention error conditions or that the object must exist, but the output schema likely handles return values. Minor gap for a low-complexity tool.

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 only provides a title 'Object Name' and type string, with no description. The tool description adds meaning by clarifying that object_name is 'the name of the object to get information about.' This compensates for the 0% schema description coverage.

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 purpose: 'Get detailed information about a specific object in the Blender scene.' This is a specific verb (get) + resource (object) + scope (specific object), which distinguishes it from the sibling tool get_scene_info that targets the whole scene.

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 usage—you use it when you need info about a specific object—but it does not explicitly mention alternatives or when not to use it. No reference to get_scene_info or other sibling tools for broader context, so only implied guidance.

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