get_blueprint_variable_defaults

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

With no annotations, the description carries the burden and does so well: 'Read' signals side-effect-free access, and the Returns section discloses the exact shape, including that cdo_value is optional and that both asset-stored and live CDO values are returned. It does not cover errors or edge cases, but for a read-only getter this is strong behavioral disclosure.

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 front-loaded with a one-sentence purpose, then organized into Args, Returns, KB, and Example sections. Every section earns its place and there is no filler or duplication of the schema.

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 two-parameter read tool the description is nearly complete: it documents parameters, return structure, optional filtering, a KB pointer, and an example. It stops short of describing failure behavior for unknown blueprint/variable names, but that is an edge case rather than a gap in core invocation guidance.

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%, so the description must supply meaning for every parameter, and it does: blueprint_name is the asset name, variable_name is an optional filter, and leaving it empty returns all variables. The example also demonstrates the expected asset path format.

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 opening sentence uses a specific verb and resource: 'Read the default value(s) of Blueprint member variables.' It then sharpens the scope by distinguishing the asset-stored default from the live CDO value, which is clear enough to tell apart from sibling getters/setters like get_blueprint_variables and set_blueprint_variable_default.

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: call this when you need Blueprint variable defaults, and use variable_name to narrow results. However, it never names sibling tools or states when NOT to use this tool versus get_blueprint_variables or set_blueprint_variable_default, so usage guidance is mostly inferred.

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