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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to establish safety. It does add real value by disclosing the return shape (0-100 score, risk drivers, one of three recommendation bands) since there is no output schema. However, it says nothing about how a 'short description' is mapped to parameters, whether omitted optional inputs default or lower confidence, or whether the score is deterministic or advisory.

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, no waste, with the core action front-loaded and the output contract following immediately. Nothing should be removed.

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 seven inputs, no output schema, and no annotations covering results, the description does the necessary work of explaining what comes back. It falls short only on the interaction between the single required parameter and the six optional ones, which an agent would need in order to decide how much detail to supply.

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 every parameter including all enum values is already documented in the schema; baseline 3 applies. The description only gestures at 'a short description of its situation' and adds no per-parameter meaning, nor does it clarify that system is the sole required input while the other six are optional enrichment.

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 and resource: 'Score the structural risk of a company's current ERP from a short description of its situation'. This distinguishes it from the estimation siblings (estimate_migration, estimate_bridge_to_cloud_savings), though it never names those siblings 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?

Usage is implied by 'from a short description of its situation' — the agent infers it should call this when it has qualitative ERP context and wants a risk verdict. There is no explicit when-not guidance, no mention of alternatives like estimate_migration, and no statement about prerequisites such as which inputs matter most.

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