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

With no annotations provided, the description adds useful context like the project_key fallback behavior and the fact that it returns a JSON string. However, it doesn't disclose error handling, permission requirements, or explicitly state that the operation is read-only, leaving the safety profile mostly to inference from the name.

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 compact and well-structured, with a clear first line stating the action, followed by Args and Returns sections. Every sentence is meaningful and there is no redundancy or fluff.

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 getter with an output schema, the description sufficiently covers the invocation and return type. However, it omits details about what the configuration contains or potential error scenarios, and the lack of annotations leaves some context missing. Still, given the simplicity, it's nearly complete.

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 description explains the single parameter meaning (project key as tenant ID) and its resolution behavior (uses global tenant_id if not provided). This goes well beyond the bare schema type and default, fully compensating for the 0% schema description coverage.

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 uses a specific verb ('Get') and a clear resource ('Blocks Data Gateway configuration'), making the primary purpose unmistakable. It distinguishes itself from sibling 'configure_blocks_data_gateway' through the action word, though it doesn't explicitly contrast with other read-only tools.

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, no prerequisites, and no mention of complementary tools. The only clue is the name itself, which implies retrieval but does not offer decision-making context.

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