get_object_info

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

No annotations exist, so the description must fully disclose behavior. It only says 'Get detailed information' without explaining what information is returned, whether it is read-only, or any side effects. This is insufficient for safe agent invocation.

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 short (two sentences plus parameter details) and front-loaded with purpose. Every sentence adds value, and the parameter explanations are concise yet informative. No redundancy.

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 no output schema, the description should clarify what 'detailed information' includes (e.g., mesh data, transforms, materials). It also fails to mention any prerequisites or object types. For a tool with sibling get_scene_info, this gap hinders the agent from selecting it correctly.

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 description adds meaning beyond the input schema, which has no parameter descriptions (0% coverage). It explains object_name as 'the name of the object' and user_prompt as 'for telemetry,' providing necessary context. However, it could add examples or constraints.

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 'Get detailed information about a specific object in the Blender scene,' which clearly identifies the verb (Get), resource (detailed information about a specific object), and context (Blender scene). This distinguishes it from sibling tools like get_scene_info, which operates on 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?

No guidance provided on when to use this tool vs. alternatives (e.g., get_scene_info). The description implies the tool is for individual objects but does not explicitly state usage context or when not to use it.

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