get_object_info

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

No annotations are provided. The description only states that it gets information, implying a read-only operation, but does not explicitly confirm safety, side effects, or what 'detailed information' includes. The agent is left to assume it is non-destructive without confirmation.

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 very concise, consisting of a single sentence and a parameter list. Every word contributes meaning, and there is no redundancy or fluff.

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 is incomplete for a simple information retrieval tool. It does not describe what 'detailed information' includes (e.g., properties, transform, modifiers), nor does it state prerequisites (e.g., object must exist) or behavior if the object is not found. Missing output schema makes this more critical.

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 descriptions for its only parameter. The tool description provides a minimal description ('The name of the object to get information about'), which adds value. However, it lacks details like case sensitivity, format, or constraints. Given low schema coverage, the description compensates minimally.

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 'Get detailed information about a specific object in the Blender scene.' The verb is specific (get) and the resource is well-defined (object information in Blender scene). It distinguishes itself from siblings like get_scene_info and other asset-specific getters.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives like get_scene_info or other getters. There is no mention of prerequisites or contextual cues for selection.

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