List Spaces

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds minimal value by stating it returns a formatted list of accessible spaces, which is expected. No additional behavioral traits (e.g., pagination, rate limits) are disclosed.

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 brief (two sentences) but includes a redundant return type line ('Returns: str: ...') that does not add value since an output schema exists. The first sentence is concise and focused. Could be tighter by removing the docstring-style return.

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?

Despite rich annotations and an output schema, the description omits critical details about parameter usage (e.g., possible space_type values, effect of page_size). The tool is a list operation, but the description does not clarify filtering or pagination behavior, leaving the agent underinformed.

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 has three parameters (user_google_email required, page_size with default 100, space_type with default 'all'), but the description provides no explanation of their meaning or expected values. Schema description coverage is 0%, so the description needed to compensate but failed entirely.

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 it lists Google Chat spaces (rooms and direct messages) accessible to the user. The verb 'lists' matches the tool name, and the resource 'Google Chat spaces' distinguishes it from sibling tools that list other entities like calendars or drive items.

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 no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It only states what it does, leaving the agent to infer usage context from the tool name alone.

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