roi_projector

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

Adds value beyond annotations by detailing output structure (current leak estimate, recovery levels, payback period, 12-month projection). Annotations already cover safety traits; description complements with behavioral specifics.

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?

Well-structured: intro, usage note, Args, Returns. Every sentence is informative and no verbosity. Front-loaded with 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?

Covers input parameters, usage order, and output summary. Output schema exists externally, so detailed return structure not required. Slightly lacking in output schema detail but sufficient.

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?

Given 0% schema coverage, the description fully explains each parameter: monthly_revenue ('any currency'), revenue_leak_score ('Business Health Score from diagnosis 0-100'), team_size, currency, lang. Adds essential semantics missing from 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?

Description clearly states it projects ROI from diagnosis recommendations, with specific verb 'Project ROI' and resource 'diagnosis recommendations'. It distinguishes from siblings by indicating usage order.

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?

Explicitly says 'Use AFTER business_diagnose or action_plan', providing clear context. Lacks explicit 'when not to use', but the instruction is strong.

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