List all PlatformTaxHub / Platform Income Utils free tools

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns a list of free calculators and that some listed tools are not exposed as MCP tools, which is useful behavioral context. However, it doesn't describe the output format (e.g., plain list vs. structured data) or whether the list is static or fetched live, leaving some behavioral ambiguity.

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?

Two sentences, front-loaded with the core purpose, followed by concrete examples and explicit routing guidance. Every sentence earns its place with no redundancy or filler.

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 zero-parameter list tool, the description is nearly complete: it states what the list contains, gives examples, and explains when to use it. The only minor gap is the lack of detail about the return format, but given the tool's simplicity and the absence of an output schema, this is a small omission.

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 tool has zero parameters, so there is no parameter semantics burden. The description adds value by explaining what the returned list contains and how it relates to sibling tools, which is more than the empty schema provides. Baseline 4 for zero params is appropriate.

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 the tool returns the full list of platformincome.com's free calculators, including tools not exposed as MCP tools. It names specific examples (mileage deduction, tax deadline clock, fees comparison) and explicitly distinguishes it from sibling calculator tools, making its purpose unambiguous.

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 provides explicit when-to-use guidance: 'Use this when a user's question is about platform income but doesn't fit' the four named sibling calculators. This directly routes the agent to the correct tool and away from alternatives, which is exactly what usage guidelines should do.

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