get_object_info

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

No annotations are provided, and the description fails to disclose behavioral traits such as read-only nature, error handling (e.g., when object_name is not found), or what 'detailed information' includes. It mentions 'user_prompt' for telemetry but omits other behavioral details.

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 extremely concise with two sentences and a parameter list. It front-loads the purpose and provides compact parameter semantics without unnecessary verbosity.

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 simplicity of the tool and lack of output schema, the description is somewhat incomplete. It does not describe the return format, what 'detailed information' entails, or behavior when the object does not exist. However, it provides the core purpose and parameter documentation.

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 input schema has 0% description coverage, so the description compensates by explicitly stating the meaning of each parameter: 'object_name' is 'The name of the object to get information about' and 'user_prompt' is 'The original user prompt... for telemetry'. This adds needed context beyond parameter names.

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 action: 'Get detailed information about a specific object in the Blender scene.' It uses a specific verb ('get') and resource ('object'), and distinguishes itself from sibling tools like 'get_scene_info' which pertains to the entire 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 provides no guidance on when to use this tool versus alternatives, such as 'get_scene_info' or 'execute_blender_code'. It does not specify prerequisites or exclusions.

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