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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds real value with the none-listed fallback, the Creator-only constraint for Google Sheets, and the publish-blocking dependency for FileUpload form fields. It does not discuss pagination or limits, which keeps it out of the top band.

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?

Four dense sentences, front-loaded with the return shape before the usage constraints, with essentially no filler. Slightly long but every sentence carries operational information.

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 no output schema, the description usefully inlines the return structure ({items: [{id, type, name, connectedRiddles}]}) and the key publish-time constraints. It omits edge behavior such as what an empty result means per type or ordering, but the essentials for correct invocation are present.

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 both the type filter and projectId scoping are already documented in the schema (including the 'omit for both' / 'omit for API-key-scoped project' semantics). The description adds no parameter-level detail beyond what the schema provides, so baseline 3 applies.

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 precise verb and resource ('Lists the Google Sheets and webhook integrations of a project') and even shows the return shape. It is clearly distinct from siblings like project_list or riddle_list, so an agent can select it without ambiguity.

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?

It explains the downstream purpose of the result (the 'name' value feeds publish.integrations.googlesheets / .webhook) and gives a fallback instruction when nothing is listed (ask the user to add a Sheet in the Creator). It stops short of naming alternative tools or explicit when-not-to-use conditions, but the workflow context is strong.

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