ERP Selection Tool

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

No annotations are provided, so the description must carry the full burden. It states only the high-level scoring action but does not disclose how scoring works, what the output looks like, what assumptions are made, or any side effects. This is a substantial gap for a tool with no annotation support.

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 single-sentence description is concise and front-loaded, but it is under-specified. While not verbose, it sacrifices necessary detail, making it minimally adequate rather than well-structured.

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 8 parameters, no annotations, and no output schema, the description is severely incomplete. It neither explains the scoring logic, the meaning of parameters in context, nor what return value the agent can expect. This is inadequate for effective tool selection and invocation.

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%, and the description provides no parameter information whatsoever. All 8 parameters (with enums and defaults) are left entirely to the schema, so the description adds zero semantic value beyond the structured fields.

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 uses the specific verb 'Score' and names the resource ('your best-fit ERP shortlist across 10 systems'), clearly indicating this tool evaluates and ranks ERP options. It is distinct from sibling tools, which are calculators, so the purpose is unambiguous.

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 context of selecting an ERP is implied by the title and description, but there is no explicit statement about when to use this tool versus other calculators or the odoo-specific tools. No exclusions or alternative tools are mentioned, leaving usage guidance to inference.

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