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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds behavioral context beyond these annotations by stating that results may change over time and may include third-party offers when enabled, and that the application process happens on the issuer's own platform. This gives the agent useful expectations about volatility and workflow.

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?

The description is three sentences with no unnecessary words. The first sentence states the core action, the second describes outputs, and the third adds time/third-party context and the application flow. Every sentence contributes meaningful information.

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?

Given the tool's low complexity (two simple optional parameters), full schema coverage, strong annotations, and an output schema, the description fully covers the tool's purpose, expected results, result variability, third-party involvement, and downstream user action. No critical information seems missing for an agent to select and invoke the tool correctly.

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 input schema already provides full descriptions for both parameters (creditScore and rewardsType) with ranges and enum values, giving 100% schema coverage. The description merely names these criteria without adding additional syntax, constraints, or format details. Thus the description adds no significant semantic value beyond the schema.

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 uses the specific verb 'Search' and clearly identifies the resource as 'SecureLend's lender database for personal credit card offers.' It specifies the matching criteria (credit score, preferred rewards type) and distinguishes itself from sibling tools by focusing on personal credit cards, not business cards or loans.

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 description clearly implies when to use the tool: when a user needs personal credit card offers based on credit score and rewards preferences. It does not explicitly name alternatives or exclusions, but the context is unambiguous given the sibling tool names. It could be improved by explicitly directing users to business card tools for business needs.

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