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

With only readOnlyHint available, the description does real work: it discloses the security findings are ordered worst-first, that package code is immutable, and — critically — that the analysis covers permissions, not code safety ("nothing here says the code is safe"). That caveat prevents a serious misreading of the output. It does not mention batching limits or failure behavior, which the schema partially covers.

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 verb and resource are front-loaded, which is good, but the body is one enormous run-on sentence with deeply nested parentheticals that blur the security findings together. For the amount of genuinely useful content it is defensible in length, but splitting the enumeration into a structured list would make it far easier to scan.

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?

There is no output schema, so the description must carry the return contract — and it does thoroughly, naming every field group plus the ordering of security findings and what those findings mean. The one interpretive limit it flags (permissions vs. code safety) is the most important caveat for this tool. Only minor gaps remain, such as behavior on an invalid or non-component address.

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 100%, so both parameters are already fully documented, including the enum for network and the cap of 10 addresses. The description only restates that a component looks like component_… and that several can be read at once, adding no format or semantics beyond the schema. Baseline 3 is appropriate.

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 concrete verb and resource ("Reads one or several Radix components") and enumerates exactly what the result contains — name, blueprint, package, ownership, roles, holdings, royalties, and a security analysis. The "same card the console's Component info section shows" anchor makes the scope concrete. It stops short of naming when to prefer get_component_state or get_component_blueprint, so sibling differentiation is only implicit.

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?

Usage is implied rather than stated: the heavy emphasis on roles, who can change things, and security findings signals this is the permissions/security overview tool. There is no explicit when-to-use or when-not, and no alternative is named even though get_component_state and get_component_blueprint sit right next to it.

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