revenue_review

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

Description states it 'manages revenue phase transitions,' implying mutability, but annotations declare readOnlyHint=true, indicating a read-only operation. This contradiction undermines behavioral transparency.

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 single sentence that front-loads the purpose ('Weekly Revenue Review'), but it could be more structured for clarity.

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 no output schema, the description should explain the return value, but it does not. It also fails to resolve contradictions with annotations, leaving important gaps for the agent.

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?

With no parameters and 100% schema coverage, the baseline is 4, but the description mentions 'selected pipelines' without any corresponding selector parameter, creating confusion about how to invoke the tool.

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 clearly states it compares actual revenue vs projections and manages revenue phase transitions, identifying the specific resource (revenue) and actions. However, it does not fully distinguish from sibling tool 'update_pipeline_state' which might also handle phase transitions.

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 explicit guidance on when to use this tool versus alternatives like 'update_pipeline_state' or other revenue-related tools. The agent must infer usage from context alone.

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