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

Annotations already cover safety (readOnlyHint=true), so the bar is lower. The description adds genuine context beyond that: it discloses the return content (functions/methods with argument names and types) despite there being no output schema, and explains the auto-resolution behavior for component addresses.

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?

Two tight sentences with zero waste; the output definition is front-loaded and the calling convention follows immediately. Every clause carries information.

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?

With no output schema, the description compensates by describing what is returned, and annotations cover the safety profile. It is nearly complete, lacking only error/failure behavior for invalid addresses.

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 100%, so all three parameters are already documented, including 'Ignored for component addresses' for blueprintName. The description restates the address/blueprintName relationship but adds little syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource: returns the 'callable interface' of a component or package blueprint, specifying it lists every function/method with argument names and types. This clearly distinguishes it from state-oriented siblings like get_component_state or lookup_entity, though it never names an alternative explicitly.

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 second sentence gives practical calling guidance (pass a component address, or a package address plus optional blueprintName), and notes the blueprint is resolved automatically. However, it offers no when-to-use vs. when-not guidance against siblings such as get_component_state or inspect_address.

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