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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that this returns the complete content of the source (every synced page/document), which is useful behavioral context about output volume, though it does not discuss result size limits or pagination for large sources.

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 short sentences, front-loaded with the use case and example, followed by the alternative routing and an explicit exclusion. Every sentence carries actionable information with no filler.

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 one required parameter, full schema coverage, and read-only annotations, the definition is nearly complete; it covers what is returned and how to obtain the ID. The only gap is guidance on volume or pagination when a source contains many documents, which matters for a 'read everything' tool, but no output schema exists and annotations carry the safety profile.

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 coverage is 100% and the single source_id parameter is already documented as a UUID obtained from list_sources. The description reinforces that provenance ('get the source ID from list_sources') but adds no format or syntax detail beyond the schema, so baseline 3 is appropriate.

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 and resource ('returns every synced page or document from that source') and scopes it to one connected source. It explicitly distinguishes itself from search_knowledge and get_brand_context, so an agent can separate it from siblings without reading schemas.

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?

Gives a concrete trigger ('full content of one connected source', with a user-phrase example), names the alternative for specific questions (search_knowledge), and explicitly excludes brand voice/identity in favor of get_brand_context. When-to-use, when-not-to-use, and alternative routing are all present.

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