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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that it "opens nothing by itself" and returns screens/buttons/fields, which is real behavioral context beyond the annotations. It is thin, though – nothing about the shape or size of the returned instructions or what happens on failure.

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 core behavior is front-loaded in the first sentence, which is good. But the trailing sentence about PeoplePerHour's official API is redundant and awkwardly constructed ("PeoplePerHour's official API: PeoplePerHour has no public API..."), and the parenthetical date adds little for an agent deciding whether to call it.

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 no params and no output schema, the description must fully carry both the trigger and the return contract. It explains that the return is a step-by-step guide, but it never resolves the obvious ambiguity of a \"get offer\" tool with no way to specify an offer, nor does it clarify whether the guide is generic or scoped to the user's current context.

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; the schema is trivially complete. A 4 is the baseline here – the description does not need to explain inputs and correctly avoids inventing any.

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 states the resource ("Offer in PeoplePerHour") and clarifies that the tool returns a step-by-step how-to rather than data. However, that clarification cuts against the tool name "get_offer", and the description never distinguishes this from sibling tools like peopleperhour_search_offers or cotlet_app_guide, which plausibly serve overlapping guide/search purposes.

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?

There is an implied workflow ("then do it with the cotlet_browser_* tools in the user's PeoplePerHour Cloud Browser") that tells the agent what to do after calling. But it never says when to prefer this over cotlet_app_guide or peopleperhour_search_offers, and no prerequisites or exclusions are given.

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