Agent Feedback Loop

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully explains the ranking logic (usage + feedback) but omits whether results are cached, paginated, or what occurs if the lookback period exceeds available data. It also does not describe the return structure.

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?

Front-loaded with clear purpose statement. Uses docstring-style Args section which is slightly informal for MCP but efficient given parameter simplicity. No wasted words, though the param documentation could be redundant with schema if schema were properly documented.

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?

Adequate for the input complexity (2 optional integers) but incomplete regarding output. No output schema exists, yet the description only hints at results with 'Shows which tools...' without clarifying the data structure, fields returned, or whether empty results return [] or error.

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% (titles only, no descriptions). The Args section documents both parameters sufficiently: 'days' is explained as the lookback period with default noted, 'limit' as max results with default noted. This compensates for the schema's lack of descriptions.

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?

States specific verb (Get) + resource (trending MCP tools) + ranking criteria (recent usage and feedback). Second sentence clarifies it surfaces both usage volume and ratings. However, it does not explicitly differentiate from sibling 'get_best_tools' which likely overlaps in functionality.

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?

Provides no guidance on when to use this versus 'get_best_tools' or 'get_tool_quality', nor does it mention prerequisites or exclusions. The agent must infer that 'trending' implies time-based popularity while 'best' implies overall quality.

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