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

Goes beyond the annotations by disclosing the asynchronous fallback return shape ({status:pending,job_id}) and the thread-context round-trip requirement, which the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) do not convey. It adds real behavioral value, though it omits auth/permission expectations.

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?

Tight, front-loaded and dense with no filler; the sync/async branch and thread contract come early. The telegraphic phrasing ('Full pipeline (schema, queries, analysis)') is slightly cryptic but earns its space.

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 carries the burden of return-value disclosure and does so for the async path ({status:pending,job_id}, thread_id in the result) plus the polling follow-up. It is nearly complete for an open-world agent-invocation tool, with only auth/permission context missing.

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%, so parameters are already documented, but the description adds semantics the schema lacks: the thread id must be a stable UUID sent on every call and the returned thread_id must be re-sent later. That threading contract is genuinely additive.

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+resource ('Ask the agent') and elaborates the scope with 'Full pipeline (schema, queries, analysis)', so the agent knows this is a general query entry point rather than a status/response reader. It stops short of explicitly contrasting with the 'help' sibling, so sibling differentiation is only partial.

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?

Explains the sync/async branching ('Sync within deadline_seconds; else {status:pending,job_id}') and routes the caller to the correct alternatives ('poll request_status/read_response'). This is clear when-to-use context with named alternatives, though it never states when not to use 'ask' versus 'help'.

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