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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that: it discloses result ordering (newest first), which fields are returned, and an auth constraint ('Needs the user's Cotlet API key with access to this app'). Pagination/result-limit behavior is not disclosed.

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?

Purpose, guidance and prerequisite are ordered sensibly with no wasted sentences. However the returned-field list is stated twice ('with title, price and status' then 'with title, price and whether each is live'), which is mild redundancy in a three-sentence description.

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 with no output schema, the description covers the fields returned and the auth requirement well. It omits any note on result count limits or pagination for a list that has explicit ordering, which is the one remaining gap.

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 no parameters, so the baseline is 4. There is nothing in the schema for the description to clarify, and it does not attempt to invent parameter semantics.

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 and resource ('Lists the fixed-price Offers on your profile') plus concrete returned fields and ordering ('newest first, with title, price and whether each is live'). An agent can distinguish this read/list operation from the sibling peopleperhour_create_offer without opening either 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?

'Use it to check what you already sell before creating another' gives a clear usage context and implicitly routes to the create_offer sibling. It stops short of naming the alternative tool or stating when not to use it, so it is clear context rather than explicit routing.

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