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

With no annotations available, the description carries the full burden of behavioral disclosure. It indicates the query type and roughly what the result covers, but it does not state whether this is a read-only search, how results are returned, or whether there are any limits or prerequisites.

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?

The description is brief and mostly front-loaded with the subject, but it reads as fragmented sentence fragments rather than a clear explanatory statement. It is concise without being fully informative.

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 search tool with no annotations and no output schema, the description should at least clarify return behavior and how q maps to results. It provides superficial context but leaves essential operational details unspecified.

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 compensate for the bare 'q' string property. 'Free text or code' adds some meaning, but it does not explain requiredness, query format, examples, or edge cases like an empty query.

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 identifies PCC as the subject and hints at the scope ('what it is, what you get, what you pay'), but it lacks an explicit verb like 'search' or 'find'. The tool name supplies the missing action, so the purpose is inferable rather than clearly stated.

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 instead of the many sibling search tools, such as pcc_search or aware_get. The alias note ('AWARE is a retired alias') is context, not a usage directive.

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