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

The annotations already mark the tool as read-only and idempotent, and the description adds the critical authentication requirement (Bearer token) and describes the output structure (outcome and source). This goes beyond the structured data and gives the agent necessary operational details.

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 front-loaded with its purpose and then expands with illustrative questions and return categories. While it includes some redundancy (e.g., 'Lets the user just ask'), each sentence contributes context, and it is not overly verbose.

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 read-only tool with a single parameter and no output schema, the description covers the return value in detail (outcome and source), explains authentication, and gives typical use cases. No major gaps are apparent, though it could mention error handling or rate limits, which is not required for this complexity.

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 only parameter, windowDays, is fully described in the schema (default 30, max 90). The description does not add any additional meaning or constraints beyond that, so it meets the baseline for high schema coverage.

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 opens with 'Get YOUR own Pickrate agent analytics', clearly stating the verb and resource. It further elaborates with example questions about traffic, signups, and revenue, and explicitly distinguishes this from leaderboard or pick-rate tools by emphasizing 'YOUR own', making its purpose unmistakable.

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 description provides context that this tool is for users who want to 'just ask instead of opening a dashboard', indicating when it's appropriate. However, it does not explicitly mention alternatives or when not to use it, such as pointing to getLeaderboard for global rankings, so it stops short of full exclusion guidance.

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