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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the output is 'deterministic' and 'free'. That is real behavioral context. However it never states the operation is read-only/personal-scope, nor any auth requirement or rate limit, so coverage remains partial.

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?

A single em-dash-delimited sentence, front-loaded with 'Bid coach', with no redundant sentences. Dense but every clause earns its place.

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 read/report tool with a fully documented single parameter and no output schema, the description reasonably conveys the returned contents (bids, wins, medians, coaching lines). It omits usage timing and any scoping/auth caveats, leaving it adequate but not complete.

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?

Only one parameter exists and schema description coverage is 100%; the api_key is even documented as deprecated with header guidance. The description adds nothing about parameters, so the baseline 3 for high schema coverage applies.

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 concrete resource and scope: 'your decided bids per capability over 180 days', enumerating what's returned (bids, wins, median vs median-winning bid, coaching lines). An agent can tell this is a personal bid-performance report distinct from listing tools like bids_list. It stops short of explicitly naming which sibling to use instead.

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 no when-to-use or when-not-to-use guidance. Nothing tells the agent how this differs from bids_list or jobs_my_bids, or when the coaching report is the right call versus a raw listing.

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