get_object_info

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

With no annotations, the description must convey behavioral traits. It only states that it 'gets information,' which implies read-only, but it doesn't explicitly disclose that there are no side effects, error conditions, or permissions required. This is minimal disclosure beyond the basic action.

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 a short paragraph that leads with the purpose and then lists parameter details. Every sentence serves a purpose with 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?

The description explains inputs but not what 'detailed information' includes or the return format, and it doesn't mention failure handling (e.g., missing object). Since there's no output schema, this gap leaves the agent uncertain about the tool's result.

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 no property descriptions (0% coverage), so the description compensates by explaining both parameters: object_name is the target object, and user_prompt is for telemetry. It adds meaning to user_prompt beyond the schema, though object_name's explanation is tautological.

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 function: retrieving detailed information about a specific object in the Blender scene. The verb 'Get' and the resource 'object' differentiate it from scene-level tools like get_scene_info or execute_blender_code.

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 when object information is needed, but it does not explicitly mention alternatives or when not to use it. No exclusions or comparisons with sibling tools are provided, leaving the timing of use to inference.

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