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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuine value beyond that by stating the tool "creates no account and sends no text" and that joining "asks only for your business details" — a privacy and side-effect disclosure the agent cannot get from 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?

Two long sentences, and the first is a marketing description of the InstaBids marketplace that does not describe what this tool does. The actionable content — what is returned and what the caller must do with the links — is buried in the second half rather than front-loaded.

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 tool with an output schema, the description is nearly complete: it enumerates the returned content (join steps, availability, alias privacy, job-texts status, links) and states the caller's follow-up action. The only gap is that it never scopes itself against the sibling how_instabids_works, leaving overlap unresolved.

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 no parameter meaning to convey; the baseline is a 4. The description does note that joining requests only business details, but that refers to the external signup flow, not to any input this tool accepts, so it adds little parameter-level value.

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 core verb and resource are specific: "Get the contractor join steps, availability, alias privacy, job-texts status and links to join or ask for text alerts." It also distinguishes itself behaviorally from an enrollment action ("this tool creates no account and sends no text"). However, the opening half of the description is a homeowner-facing marketplace pitch rather than a statement of this tool's purpose, which dilutes the clarity.

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?

It gives clear operating context: "Hand over the links so the contractor signs up and asks for texts themselves." That tells the agent what to do with the output. It does not explicitly name sibling tools such as how_instabids_works as alternatives, so the routing guidance between the two overview-style tools is left to inference.

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