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

Annotations already declare readOnlyHint, idempotentHint and non-destructiveness, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey: the strict single-Location scoping and the no-fan-out rule, which prevents a common misuse on multi-location connections. Pagination and error behavior remain unstated.

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 short, front-loaded sentences: purpose first, then the one constraint that matters. Every sentence earns its place; only the docstring backtick escaping adds minor visual noise.

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?

With an output schema present, return values need no explanation, and the annotations cover the safety profile, so the description is close to sufficient. A note on whether card numbers or sensitive identifiers are exposed would round it out for a financial-data listing tool.

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?

Schema coverage is 0%, so the description carries the full burden for the single parameter, and it does so well: it identifies ``location`` as a single Rent Manager Location ID, marks it optional, and states the condition under which it becomes required. It stops short of describing the ID format or what the empty-string default means.

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 ("List the credit cards defined on this Rent Manager database") with a clear scope of the local database. It implicitly separates itself from get_credit_card_attachments, but does not explicitly name that or any other sibling, so an agent must infer the boundary.

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?

Gives a concrete usage condition: ``location`` is required when the connection has several Locations, and the tool never fans out across Locations. It also routes the agent to ``list_locations`` to discover IDs. What's missing is an explicit 'do not use this when you want X' statement or a named alternative for card-level detail.

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