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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the return shape (array of records) and filter/pagination support, but not much else beyond what schema and annotations supply. A 3 is appropriate given the lower bar when annotations are present.

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 tight sentences with the core purpose front-loaded, followed by return shape, filters, and the routing rule. No wasted words.

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 not be explained, and annotations carry the safety profile; the description covers purpose, filters, and the sibling boundary. Minor gap: no note on default page size or behavior for large unpaginated sets, though the schema's limit/offset descriptions partly cover this.

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 description coverage is 60% (limit, offset, updated_gte documented; sort, order not). The description enumerates the same filter params (updated_gte, sort, order, pagination) but adds no syntax, format, or default detail beyond what the schema already provides. Baseline 3 fits.

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 ('List') and resource ('secretsmanagers from the connected account') and explicitly distinguishes itself from the sibling get_unified_secretsmanager. An agent can route between list and get without opening either 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?

Explicit when-to-use ('browse or search many secretsmanagers') plus a named alternative for the single-item case ('to fetch a single secretsmanager by its ID, use get_unified_secretsmanager'). Nothing is left to inference.

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