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

No annotations are given, and the description contains no behavioral details. It does not disclose whether the tool reads, mutates, returns static data, or has any side effects, permissions, or rate limits.

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 three-word fragment, not a complete sentence. While very brief, it is under-specified and provides no structure, making it an example of under-specification rather than effective conciseness.

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 no output schema and no annotations, the description must carry full context. It fails to state what the tool returns, how it operates, or what the methodology entails, making it wholly inadequate even for a no-parameter tool.

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 input schema has zero parameters, so there are no parameter semantics to explain. According to the 0-params baseline, the schema is complete and the description does not need to add parameter details.

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 'Risk scoring methodology' names a concept but doesn't specify an action or resource. It distinguishes from siblings only by the phrase 'risk scoring,' yet the tool name 'methodology' makes the description largely a restatement with no clear verb or outcome.

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?

No guidance is provided on when to use this tool versus siblings like 'risk_assessment' or 'compare.' There is no mention of alternatives, prerequisites, or exclusions.

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