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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'package stats' without mentioning what stats are returned, whether it queries live data, rate limits, or error behavior. This is insufficient disclosure for a tool with no annotation support.

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 a single compact line that front-loads the most important information: the ecosystem and the input format. There is no wasted text, and every part contributes to understanding the tool.

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 simple one-parameter lookup with an output schema, the description provides the core invocation hint and ecosystem label. However, it lacks detail about the nature of the stats returned and offers no usage guidance, leaving a moderate gap in completeness.

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 schema only defines q as a string with default '', providing no description at 0% coverage. The description's '(vendor/pkg)' adds the crucial expected input format, which compensates well for the missing schema documentation and tells the agent exactly how to form the 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 clearly identifies the tool as providing PHP/Composer package stats for a vendor/package resource. It distinguishes itself from sibling ecosystem tools like npm, pypi, and crates by naming the specific ecosystem, though it lacks an explicit verb phrase.

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?

The 'PHP/Composer' qualifier implies when the tool is relevant, but there is no explicit guidance on when to use it instead of sibling package/registry tools. No alternatives or exclusions are mentioned, leaving the agent to infer usage from the naming convention.

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