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

Annotations already declare the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds the endpoint and parameter names but does not disclose additional behavior such as pagination defaults, sorting, or error handling. It adds some value beyond annotations but is not rich in behavioral context.

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 a single, focused sentence that front-loads the primary purpose and includes the endpoint and optional parameters. There is no irrelevant information or redundancy.

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 a rich annotations set and an output schema, the description need not explain return values. It adequately conveys the operation and optional parameters. However, it could be slightly more complete by mentioning pagination behavior or filtering nuances, though these are mostly covered by the schema.

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 100%, so the schema already describes all four parameters (tab, page, query, per_page). The description only paraphrases parameter names (page, search query, tab, page size) without adding semantic meaning beyond what the schema provides.

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 clearly states the tool lists agents in the authenticated workspace via a specific endpoint, distinguishing it from siblings like list-owned-bots or list-agent-versions. The verb 'List' and resource 'workspace agents' are specific and unambiguous.

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 provides clear context for what the tool does but does not explicitly state when to use it over alternatives. It mentions the endpoint and optional parameters but lacks exclusion or alternative recommendations, which would be helpful given similar sibling tools.

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