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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: an authorization prerequisite (access right on the named robot, or on at least one robot when none is given) and a per-robot scope limit. It does not describe what the analysis returns or its size/shape.

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 sentences with no filler; the scope constraint is front-loaded immediately after the purpose. The trailing clause 'when none is' is slightly elliptical but the total length is well matched to the tool's simplicity.

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 read-only, non-destructive two-parameter tool with full annotation coverage this is close to sufficient, but with no output schema the description never indicates what a 'block analysis' actually yields, and it leaves the robot_id-omitted behavior to inference.

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 carry the parameters. It partly does: the parenthetical block list effectively enumerates valid block_id values, and 'when none is [named]' signals robot_id is optional and falls back to a broader scope. But it never states the block_id format, what happens when robot_id is omitted (aggregate across robots?), or the difference in result for each case.

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 ('Analyse') and a specific resource ('one software block'), and enumerates the block domains (OS, middleware, runtime, control, fleet), which separates it from hardware_get_block_analysis and mechanical_get_block_analysis via the software domain prefix. It never names a sibling explicitly, so differentiation is by domain naming rather than routing.

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 'for a single robot at a time' constraint and the access-right prerequisite imply when the tool applies, but there is no explicit guidance on when to prefer it over software_get_dependency_profile, software_get_robot_software, or software_get_system_status, nor any stated exclusion.

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