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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (per-account timing points and top-contributing factor), which matters since there is no output schema.

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?

A single dense sentence with the scoring model front-loaded and the output detail trailing after the semicolon. Nothing is redundant, though the sentence is long enough that a reader must parse it carefully.

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 nested-object, zero-required-parameter tool with no output schema, the description covers what the tool produces and the factors that drive ranking, and the schema fully documents inputs. Only the routing context relative to sibling scoring tools is missing.

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%, including the timing point mapping and the 50-default for missing fit/relationship/intent values, so the schema does the heavy lifting. The description only restates that the score is weighted by those four factors and adds no syntax or format detail beyond the schema.

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 pair (rank/prioritize) and resource (accounts) plus the scoring basis (weighted fit, intent, relationship, timing), which an agent can act on immediately. It does not, however, name or contrast itself with any sibling such as icp_scoring_model, which is the closest alternative.

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?

There is no when-to-use, when-not-to-use, or prerequisite guidance anywhere in the description. Given nine sibling tools in the ICP/account space, the absence of routing guidance leaves the agent to infer when this beats icp_scoring_model or lookalike_signal_generator.

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