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

Annotations already declare readOnly=true and destructive=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: credit consumption, no automatic retry, no pagination, and the idempotency-key requirement for POST searches. It stops short of 5 only because it doesn't say what happens on partial failure or how credits are debited.

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 short sentences, front-loaded with the core action before the caveats. Dense and mostly waste-free, though 'May consume credits' and the retry/pagination note could be merged into one cost/behavior clause.

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 credit-consuming execution tool with a nested free-form parameter bag and no output schema, the description covers behavior well but leaves the agent without guidance on what endpointId refers to or how to shape 'parameters'. Adequate but with clear gaps.

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 0%, so the description must carry parameter meaning. It explains idempotencyKey's purpose and hints at maxCredits via 'may consume credits', but endpointId and the free-form nested 'parameters' object are never described, leaving half the surface undocumented.

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 names a concrete verb ('Execute') and scope ('one source read or search'), which distinguishes it from the metadata siblings (get_endpoint, list_endpoints, get_capabilities, list_platforms). However, 'source read or search' is somewhat abstract and it never names the sibling it complements, so it stops short of a 5.

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 gives one real usage rule (POST search requests need a stable idempotency key) and warns that credits may be consumed, which implicitly says 'use sparingly'. But there is no explicit when-to-use vs when-not, nor any pointer to the sibling tools that supply the endpointId this tool requires.

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