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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description earns credit by adding the empty-state behavior ('profiles is empty when the account has no profile'), which is exactly the kind of edge-case context annotations cannot convey. Return-format details are legitimately omitted because an output schema exists.

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 short sentences: purpose first, safety second, edge case last. Every sentence carries distinct information and none restates the title or annotations verbatim.

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 zero-parameter, read-only, single-object getter with full annotation coverage and an output schema, the description supplies everything an agent needs: what it returns, that it is scoped to the signed-in user, and how to interpret an empty result. Nothing relevant 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description instead spends its words on return semantics, which is the right use of space for a no-arg tool.

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 plus resource ('Get the signed-in user's Tendy profile filters') and the description enumerates exactly what it returns: categories, regions, and budget range. It also anchors the tool to its sibling by naming list_my_feed as the consumer of these filters, so an agent can distinguish it from get_tender or update_my_profile without opening a 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?

The phrase 'that list_my_feed filters on' tells the agent the concrete context in which to call this tool, which is stronger than a bare description. There is no explicit exclusion clause (e.g. 'use update_my_profile to change these'), but the read-only framing and sibling naming make the boundary clear enough.

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