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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false; the description adds meaningful behavioral detail beyond this: auction ordering rules, equal-bid tie-breaking, no-bid fallback order, and the fact that bids are in ET10 and never collected. There is no contradiction with annotations.

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 description is five short sentences with no filler. It front-loads what the tool is, explains ordering mechanics, notes the bid currency and non-collection, lists return values, and states auth requirements. Every sentence adds useful information.

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, read-only, no-auth tool, the description is complete: it explains the resource, auction rules, return shape, and access requirements. There is no output schema, but the description explicitly says the tool returns each startup's position, name, bid, and rules, which is sufficient.

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 and schema description coverage is 100%, so the baseline is 4. The description cannot add parameter meaning, but it compensates by stating the return contents and behavioral rules, which is the only relevant semantic information for a parameterless tool.

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 specific resource ('public line for Turn your App into a Startup'), characterizes it as an auction, and states what it returns (position, name, bid, rules). This distinguishes it from bidding-oriented siblings like bb_startup_bid and feature_place_bid by focusing on the public line/queue view.

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 gives clear context: it is public, read-only, requires no auth, and returns line positions and rules. It does not explicitly name alternative tools or say when not to use it, but the usage context is clear enough that an agent can infer it is the correct choice for viewing the startup line.

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