Search spaces (admin)

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

The description adds meaningful behavioral context beyond the readOnlyHint, idempotentHint, and destructiveHint annotations: it runs with useAdminAccess=true, requires administrator authorization, returns PERMISSION_DENIED for non-admins, and enforces mandatory query filters. There is no contradiction with annotations.

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 dense but every sentence earns its place: purpose first, then access restrictions, then fallback, then query syntax with examples. Despite its length, it is efficiently front-loaded and contains no filler or repetition of schema details.

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?

For a 4-parameter search tool with no output schema, the description fully covers the key operational details: auth, scope, required query syntax, ordering, and alternative tool. Pagination parameters are already documented in the schema, so their absence from the description is acceptable.

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?

Although schema coverage is 100%, the description adds crucial semantics: it mandates that query must contain customer and spaceType, explains how to use displayName for name search, gives a concrete example, and enumerates valid order_by fields. This goes well beyond the schema's generic descriptions.

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 states a specific verb and resource: server-side search over all named spaces in the Workspace organization. It clearly differentiates this tool from list_spaces by emphasizing admin-only, organization-wide scope that includes spaces the caller does not belong to.

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 gives explicit when-to-use guidance: it is admin-only, requires specific OAuth scopes, and says anyone else gets PERMISSION_DENIED and should fall back to list_spaces with client-side displayName matching. This directly routes an agent to the correct alternative.

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