daz_inspect_properties

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

No annotations provided. Description explains the tool returns a JSON with property details, implying a read-only operation. However, it does not mention side effects, permissions, or error behavior. Adequate given the simple nature of the tool.

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?

Description is concise, well-structured with a summary paragraph, Args section, and Returns example. Every part is necessary and front-loaded with purpose.

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 two simple parameters and an output schema in the description, the tool is well-documented. Could mention error scenarios, but the provided example and parameter details cover typical usage.

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 coverage is 0%, but the description fully explains both parameters. It lists possible values for property_type with defaults and details for node_label. This adds significant meaning beyond the bare schema.

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?

Description clearly states 'List all properties on a node with their types, values, and constraints.', providing specific verb and resource. It distinguishes from siblings like daz_set_property and daz_get_property_metadata.

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?

Explicitly says to use this tool before daz_set_property and describes it as 'more reliable than guessing property names.' Provides clear context but does not explicitly state when not to use it.

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