get_platform_info

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

Annotations already cover readOnlyHint=true and openWorldHint=false, so safety is partly pre-declared; the description reinforces read-only and adds the genuinely new fact that no API key is needed, which annotations do not express. It also characterizes the returned content as narrative/overview rather than data records. It stops short of noting response size or shape, but clears the higher bar for an annotated tool.

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?

Three short sentences, front-loaded with the core purpose, then the operational note, then the sibling routing. Every sentence carries information an agent needs and none is redundant.

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, no-output-schema onboarding tool, the description supplies purpose, when-to-call, auth expectations, and where to go for adjacent questions — everything needed to call it correctly.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline for a no-param tool is 4. The description correctly avoids inventing filtering or formatting options.

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?

States a specific verb (get) and resource (platform overview of GoHireHumans) and enumerates the content covered: marketplace description, key facts, kinds of work, and the search-to-approval workflow. An agent can distinguish this from get_pricing_info and get_categories without opening any schema.

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?

Explicitly tells the agent when to call it ('Call this first if you are new to GoHireHumans') and routes related questions to named alternatives for fees/payment (get_pricing_info) and category slugs (get_categories). Both the trigger condition and the exclusions are stated.

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