Plan your finances by applying the 50/30/20 rule. Enter your net income to get clear amounts for needs, wants, and investments.
Calcula orçamento pela regra 50/30/20 — necessidades, desejos e investimentos a partir da renda líquida.
| Name | Required | Description | Default |
|---|---|---|---|
| net_income | Yes | Renda líquida mensal em R$ |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden, and it clearly states the operation is a calculation. The verb 'Calcula' and the explicit rule indicate a pure, side-effect-free computation, though it does not describe the exact return shape or rounding behavior.
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 one compact sentence that front-loads the action and rule, then adds the output categories and input basis. Every phrase contributes meaning, and there is no filler or repetition.
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?
For a simple one-parameter calculator, the description covers the calculation rule, the input basis, and the three output categories, which is sufficient to invoke it correctly. It does not specify the exact output format or whether values are amounts or percentages, but the 50/30/20 rule implies the allocation.
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 coverage is 100%, and the schema already documents the single parameter as 'Renda líquida mensal em R$' with a required flag and exclusiveMinimum. The description only reinforces the net-income input without adding new parameter-level detail.
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 names a specific verb and resource ('Calcula orçamento') and pins down the exact method ('regra 50/30/20') with the categories produced ('necessidades, desejos e investimentos'). This makes it clearly distinguishable from the many sibling calculator tools, even without an explicit comparison.
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 description gives clear context for when to use it: when the user wants a 50/30/20 budget allocation based on net income. It does not explicitly mention alternatives or exclusions, but the rule and the 'a partir da renda líquida' prerequisite make the intended use unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.