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

With no annotations provided, the description carries the full burden of behavioral disclosure. It lists output components but does not state whether the tool is read-only, how scores are computed, what data sources are used, or any rate limits or side effects. The predictive nature implies read-only, but this is not explicitly stated.

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 description is a single, front-loaded sentence that uses a colon to succinctly enumerate the key output components. There is zero waste; every word contributes to conveying the tool's purpose.

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?

Given the absence of annotations, output schema, and the existence of numerous sibling tools, this description is insufficient for an agent to fully understand the tool's behavior and decide when to invoke it. It provides only a high-level summary without addressing practical details like entity type support, horizon options, or comparison to alternative tools.

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?

The schema covers only 50% of parameters (entity_id has no description). The tool description does not compensate: it neither explains entity_id nor clarifies how horizon_days relates to the listed output components (score trajectory, degradation timeline). Required parameters are 0, but no guidance is given on defaults or optionality.

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?

The description 'Full predictive risk profile: score trajectory, degradation timeline, risk level' clearly indicates that the tool generates a comprehensive risk profile for an entity, listing specific output components. It distinguishes itself from siblings like predict_score or risk_forecast by emphasizing a 'full' profile, though it does not explicitly name alternatives.

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 description provides no guidance on when to use this tool versus its many siblings (e.g., risk_forecast, early_warning, scenario_forecast). There is no mention of use cases, prerequisites, or exclusions, leaving the agent to infer appropriate usage solely from the name and vague description.

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