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

Annotations already cover read-only/idempotent safety, so the description's added value is the 'as a QUALIFIER step will apply them' framing of how the criteria are interpreted, plus the Pro/Agency plan requirement. It doesn't describe output size or shape, but with no output schema and a single-record read, the gap is minor.

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?

Three compact sentences, front-loaded with the resource and contents, then the disambiguation, then the prerequisite. No filler.

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 single-parameter read with full schema coverage and full annotation coverage, the description covers purpose, contents, disambiguation, and access gating. Nothing an agent needs to call it correctly is missing.

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 100% and personaId is documented as coming from persona_list, so the schema does the heavy lifting. The description adds no syntax or format detail beyond what the schema already says about the parameter.

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 ('Full qualification criteria for one persona') and enumerates the contents (job titles, seniority, industries, size, locations, keyword rules). It also names the sibling it is not — sequence_leads_at_step — so an agent can route 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?

Explicit when-to-use ('Read this to explain why a lead did or did not qualify') and an explicit exclusion with the alternative named ('It does not say which leads qualified: for that read... sequence_leads_at_step'). The plan prerequisite is also stated.

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