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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, providing a basic safety profile. However, the description adds zero behavioral context beyond that – no mention of what data is returned, any side effects, or how the tool behaves. Given the annotations, the description adds no value beyond the structured fields.

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?

While the text is extremely short, this is under-specification rather than conciseness. The single sentence adds no information and fails to front-load any useful content. It is the antithesis of a helpful definition.

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 2 parameters, no output schema, and no description beyond the title, the definition is wholly inadequate. There is no mention of expected behavior, return values, or how to use the parameters. Even for a simple read-only tool, this is completely lacking.

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% – the parameters 'q' and 'limit' have no schema-level descriptions, and the description provides no meaning for them. An agent cannot infer what 'q' represents (query string?) or how 'limit' affects results. With 0% coverage, the description must compensate but does not.

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?

Tautological: description restates name/title.

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 guidance on when to use this tool versus alternatives. The description offers no context, no prerequisites, and no mention of how it differs from tools like pdao_services or provider_integrations.

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