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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds behavior beyond that: it rechecks publication eligibility at call time and returns a 'portfolio matching handoff', which tells the agent the input's liveness is validated server-side rather than trusted.

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 dense sentences with the trigger condition front-loaded and the negative constraints trailing, so the agent reads the use case first. It is efficient, though the identifier enumeration slightly duplicates the schema.

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?

An output schema exists, so return values need not be spelled out, and the description still gestures at the return shape ('portfolio matching handoff'). Combined with full schema coverage and rich annotations, the definition is complete enough to call correctly, with only minor room for detail on eligibility-failure behavior.

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 description coverage is 100%, so both the opaque job_id and the durable /s/<token> URL or alias are already documented in the schema. The description restates the accepted identifier forms without adding format, precedence, or error-handling detail beyond the schema, which matches the baseline 3 when structured fields do the work.

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 verb and artifact ('branded flyer downloads or factual Facebook-group copy') for a specific resource ('currently live public RxRooster anesthesia opening'). It is clearly separable from siblings like get_anesthesia_job (raw job data) and prepare_anesthesia_job_draft (draft creation) without opening any 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?

It gives an explicit trigger condition ('when a recruiter wants branded flyer downloads or factual Facebook-group copy for a currently live public... opening') and an explicit exclusion list ('drafts, unpublished openings, single-use links, private data, or automatic social posting'). The exclusions implicitly route the agent to the draft-preparation siblings.

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