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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that baseline: it does not mention whether the result is paginated (a result_cursor parameter exists), whether an ad account is required for scoping, or any rate-limit behavior.

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?

It is a single front-loaded sentence with no wasted words, which is structurally clean. The problem is under-specification rather than verbosity, so it neither earns praise nor commits a conciseness violation.

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?

An output schema exists, so return values need not be explained. Still, for a five-parameter read tool with an opaque purpose ('evidence') and zero schema coverage, the description leaves too much unsaid — no scoping rules, no pagination note, and no differentiation from overlapping console tools.

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% across five parameters, so the description carries the full burden of explaining entity_type, entity_ids, ad_account_id, result_cursor, and connection_context. It mentions none of them, leaving the agent with no guidance on enum values, ID format, pagination, or connection scoping.

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 gives a verb ('Read') and a resource ('stored entity configuration evidence'), so the general shape of the operation is clear. However, 'evidence' is unexplained jargon, and it does not distinguish itself from siblings like console_query_overview or console_export_csv. An agent knows it is reading something but not what makes this tool distinct.

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 when-to-use guidance, no prerequisites, and no reference to any alternative. The agent is left to infer that this should be called when configuration evidence is needed, but nothing in the text tells it when this is preferred over the other console_* tools.

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