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

Annotations already declare readOnlyHint/idempotentHint, so the safety profile is covered; the description still adds value by specifying which result fields map onto which /v1/recommend inputs and by asserting 'never mutates ranking CE'. This is a genuine behavioral contract beyond the annotations, though 'ranking CE' is an unexplained abbreviation.

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, front-loaded with what it lists and followed by the usage/routing contract; nothing is padding. The arrow notation and 'ranking CE' jargon are compact but slightly opaque, keeping it off a 5.

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?

There is no output schema, and the description compensates by enumerating the profile fields (outcome, risk, tax, geography, red_lines, non_cash) an agent will receive. Combined with the zero-param schema and read-only annotations, an agent has essentially everything needed to call and consume it.

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 per the rubric the baseline is 4. The description goes further by explaining how fields in the returned profiles become parameters of other tools (outcome_preference→outcome, id→values_profile_id), which is useful downstream semantics even though it is not about this tool's own input.

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?

Specific verb ('List') plus a precise resource ('static values-profile presets'), with the parenthetical clarifying it is the same catalog used by the demo environment. It implicitly separates itself from get_values_profile by being a listing, but never explicitly says how they differ, so it stops short of a 5.

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?

States an explicit trigger ('Load before recommend when the donor stated preferences') and then routes the output to two named downstream tools — /v1/recommend for the expanded fields and create_giving_intent via values_profile_id. The agent knows both when to call this and what to do with the result.

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