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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description's only added signal is the word 'live', hinting at a real-time external lookup, but it says nothing about what evidence is returned, whether failures are surfaced as errors or empty results, or any latency/rate considerations.

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?

One short sentence with no filler and the key notion ('live identity evidence') up front, so nothing is wasted. However, the brevity comes at the cost of under-specification rather than from disciplined editing.

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 and no explanation of what 'evidence' comprises, the agent cannot anticipate the return shape or interpret results. Combined with the total absence of routing guidance among six similar siblings, the definition is not complete enough to invoke confidently.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema and annotations fully define the call surface.

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 essentially restates the tool name: 'Check live provider identity evidence' adds only the qualifiers 'live' and 'evidence' beyond 'check_identity'. It never says what 'identity evidence' concretely is (credentials? registration status? contact data?) or how this differs from verify_provider, check_status, or check_payment.

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 at all, despite six sibling tools that all sound plausibly related (verify_provider, compare_providers, check_status, check_history, check_payment, canon_registry_bulk_lookup). The agent is left to guess which check to call and under what conditions.

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