startup_valuation__berkus

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

No annotations provided and description does not disclose any behavioral traits such as assumptions, return values, or required inputs. Agent has no information about what the tool computes or produces.

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?

Extremely short but at the cost of utility. It is not a proper sentence and lacks structure. Under-specification is not 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 6 parameters, no output schema, and no annotations, the description is completely inadequate. Does not explain what the tool returns, how factors are used, or the valuation method.

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?

Description does not explain any of the 6 parameters (5 required, 1 optional). Schema has 0% coverage, so description should compensate but provides no meaning for 'sound_idea', 'prototype', 'team', 'relationships', 'rollout', or 'cap_per_factor'.

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 is only '[startup-valuation] berkus', which is a reference to the Berkus method but does not explicitly state what the tool does. It fails to distinguish from sibling tools like 'vc_method' or 'dilution'.

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 guidelines about when to use this tool versus alternatives. There is no context for when Berkus method is appropriate compared to other startup valuation methods.

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