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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds some useful behavioral context (private no-store responses, uploaded text as untrusted data) but most of the text is general account policy unrelated to this specific read operation.

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 long, poorly structured block that mixes the purpose with a dozen unrelated policy statements about limits, billing, publishing, deletion, and security. Only the first sentence is directly relevant, and the rest is not front-loaded or scannable.

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 simple read tool with full schema coverage and rich annotations, the description should focus on what the operation returns and how it fits among siblings. Instead, it omits operational details (e.g., what 'last check' contains) and spends most words on account-wide policies, leaving the agent without a clear picture of the tool's output or role.

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%: the single base_id parameter is fully documented in the schema as 'The 64-character ID returned by the API.' The description adds no additional meaning about the parameter, so the baseline of 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?

The first sentence 'Read the connected source and its last check' states a specific verb and resource, but 'connected source' is vague and the description never distinguishes this tool from siblings like get_base or get_base_usage. The rest of the passage is policy boilerplate, not purpose clarification.

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?

There is no guidance on when to use this tool versus alternatives. The mention of 'Personal-account operations' is a scope hint, but it does not tell the agent which situations call for get_base_connection over get_base, get_base_usage, or connect_base_source.

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