get_object_info

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

With no annotations, the description carries the full burden of behavioral disclosure, but it does not state whether this is a read-only operation, what 'detailed information' includes, or what happens if the object doesn't exist. The telemetry note about user_prompt is minor context but not sufficient.

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 appropriately short, leading with the purpose statement followed by concise parameter explanations. The inline parameter list is necessary given the schema lacks descriptions, and there is no extraneous 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?

The tool has no output schema and no annotations, so the description must clarify what 'detailed information' includes (e.g., transform, materials, parenting). It does not, leaving the agent uncertain about the return value's completeness for its intended use.

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 supplements the schema (which has 0% coverage) by explaining object_name as the target object's name and user_prompt as telemetry context. This adds essential meaning, though object_name could further specify format or case-sensitivity, and user_prompt's intended usage is clear.

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 retrieves detailed information about a specific Blender object, using the verb 'Get' and specifying the resource. This distinguishes it from siblings like get_scene_info, which focuses on the whole scene, and other object/scene-related 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 provides no explicit guidance on when to use this tool versus alternatives (e.g., get_scene_info, get_viewport_screenshot) or any prerequisites, such as the object needing to exist. It simply states the action without contextual usage direction.

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