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

Goes well beyond the annotations by disclosing that the link opens the GetMattered documents page and requires the user's sign-in, that the PDF is downloadable from there, and how the no-resume case is reported. The 'creates nothing, shares nothing, spends no credits' line reinforces rather than contradicts the readOnly/destructive hints.

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?

Front-loads the core verb+resource in the first clause, then layers constraints and alternatives in a logical order. Slightly long — the DOCX/rendered-PDF explanation is helpful but could be tightened — yet no sentence is wasted.

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?

Zero parameters, full annotation coverage, and an output schema that carries return shape, so the description's job is behavioral context — auth requirement, no-resume outcome, sibling routing — and it covers all three. Nothing an agent needs to call this correctly is absent.

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 the baseline is 4 and there is no parameter information the description could usefully add. Schema coverage is 100% and nothing is missing.

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: the private link to the PDF of the user's base resume, with a precise definition of 'base resume' (the one every application is tailored from). It is clearly separable from siblings like getmattered_share_resume_pdf and getmattered_set_resume 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?

Explicit exclusion: 'Do not use it to make the resume public; use getmattered_share_resume_pdf.' Also names the natural next step (getmattered_get_matches) and states the behavior when no resume exists, so the agent knows both when to call it and what to do after.

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