get_object_info

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

No annotations are provided, so the description carries full burden. It describes what is returned but does not explicitly state that this is a read-only operation with no side effects. The term 'Get' implies read, but full transparency would benefit from an explicit statement.

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 concise and front-loaded: a one-line purpose followed by structured Args/Returns section. No unnecessary words, every sentence adds value.

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 covers purpose, parameter, and return fields comprehensively. It lacks error handling or edge cases (e.g., object not found), but for a simple getter this is sufficient. The output schema is mentioned, enhancing completeness.

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 single parameter 'name' is described as 'Name of the object,' which adds meaning beyond the schema (which has no description). This is adequate for a straightforward required string parameter.

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 an object,' specifying the verb 'Get' and the resource 'object.' It distinguishes from siblings like 'list_objects' (which lists names only) and other getters that retrieve node trees or scene info.

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 detailed object info is needed. It does not explicitly state when not to use or mention alternatives, but the purpose is clear among siblings.

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