working_capital_analysis__dso

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the tool is read-only or requires specific permissions. There is no information about side effects or computational requirements.

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?

While the description is short, it sacrifices essential information. A concise description should still convey core purpose or usage; here, it falls short of being useful.

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 complexity of a financial metric with multiple parameters and no output schema, the description is completely inadequate. It fails to explain what the tool returns or how inputs relate to the calculation.

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 description coverage (0%), yet the description provides no explanation of the parameters (days, revenue, avg_receivables). The description fails to add meaning beyond the bare schema, leaving an agent unable to infer correct usage.

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 '[working-capital-analysis] dso' merely restates the tool's name and category without explaining its purpose. It does not mention that DSO stands for Days Sales Outstanding or that it calculates the average collection period, which is essential for understanding the tool.

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 sibling tools like working_capital_analysis__dio or working_capital_analysis__dpo. The description lacks any context about appropriate use cases or alternatives.

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