get_geometry_nodes_status

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. It says 'check' and 'return their info' but does not state whether the operation is read-only, what happens if the object doesn't exist (error vs empty result), or the structure of the returned info. This leaves significant ambiguity for a safety-conscious agent.

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 single sentence, which is appropriately concise for a simple tool. However, it lacks any structural cues (e.g., emphasizing the required parameter or potential return shape) and is so brief that it sacrifices clarity, making it merely minimum-viable.

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?

For a tool with one parameter, no annotations, and no schema descriptions, the description is incomplete. It does not address edge cases (missing object), output format beyond 'info', or any prerequisites. An agent cannot confidently call this tool without additional assumptions.

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?

Schema description coverage is 0% (only a title 'Object Name' is given). The description does not mention object_name or its format/requiredness beyond the schema itself. The parameter name is self-explanatory, but with zero coverage the description should add context, which it does not.

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 states a clear verb ('Check') and resource ('Geometry Nodes modifiers') and implies a status-checking role distinct from siblings like get_gn_node_tree (tree inspection) or list_modifiers (all modifiers). However, it does not explicitly name alternatives or scope out what 'info' entails, so it's clear but not perfectly differentiated.

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 guidance is provided on when to use this tool vs the many Geometry Nodes-related siblings (e.g., get_gn_node_tree, apply_geometry_nodes). The purpose itself suggests a use case, but there are no explicit when-to-use/when-not-to-use instructions.

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