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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context beyond them: the hard scope boundary (never other users' data, passwords, tokens, payment or bank details), the privacy handling instruction for EEO and date-of-birth fields, and that no credits are spent. The only weakness is repetition – 'it changes nothing' appears twice, restating the annotation without adding information.

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-loaded with the scope restriction and privacy caveats, then the return payload, then the next action – a sensible ordering. It is slightly over-long because the no-change/no-credit point is stated twice and the return enumeration is verbose even though an output schema already exists.

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?

Covers scope, exclusions, sensitive-data handling, credit cost, and the follow-up action; since an output schema exists, the return-value summary is extra rather than required. Nothing an agent needs to invoke and act on this tool 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?

Zero parameters, so the baseline is 4; the description instead characterizes the payload an agent will receive (contact details, work details, five legal declarations, EEO answers, and open/guessed fields with their answering field), which meaningfully prepares the caller. No parameter syntax is needed or 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?

Opens with an exact verb+resource ('Read only the signed-in user's own application profile') and immediately scopes it ('the answers the user saved for GetMattered to type into employer application forms'), which no other sibling covers. It also names the sibling it is not (getmattered_update_application_profile), so an agent can separate read from write without opening schemas.

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 save answers; use getmattered_update_application_profile') plus a prescribed next step ('ask the user for anything still open, then getmattered_update_application_profile'). This is a full when/when-not/alternative routing statement.

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