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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is largely covered. The description adds the 0-100 bound and the concrete downstream effect on prospect batches and the email finder. It does not mention the confirm/guard flow that the schema's confirm parameter implies, so it adds some but not rich behavioral context.

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 tight sentences, front-loaded with the action and the value range, followed by the downstream consequence. No filler. The parenthetical '(0 to 100)' is efficient and earns its place by merging with the constraint.

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 three-parameter, single-value setter with no output schema, the description covers the operation, the unit/range, and the effect. The only gap is behavioral — nothing about the confirm guard — but that is documented in the schema, so an agent has what it needs.

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?

Schema coverage is 67%, with app_id and confirm already documented in the schema. The description compensates for the undocumented min_score by explaining its meaning ('the least fit score a site needs') and its range, which the schema only bounds numerically. This is meaningful added value beyond the structured fields.

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?

Names a specific verb and resource ('Set a project's fit floor') and defines the concept concretely — the minimum fit score required for autopilot's affiliate prospect batches and the paid email finder. It distinguishes itself from set_autopilot and set_autopilot_mode by being about one numeric threshold, though it doesn't explicitly contrast against them.

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?

Usage is implied rather than stated: the reference to get_autopilot ('shows it as floor and ready_sites') tells the agent how to read the current value, but there is no explicit when-to-use guidance, no prerequisites, and no exclusions relative to the sibling set_autopilot tools.

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