Rapport NavRank / ClickRank

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description's GET path is consistent with that. The description adds context by stating the report is computed on weekly clicks/visits/engagement and covers anomalies/traffic drift, but it does not disclose edge behaviors such as missing reports or date-boundary handling.

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 sentence that front-loads the resource name and follows with useful content detail and the endpoint. Minor redundancy exists between the title and the opening phrase, but there is no padding.

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?

There is no output schema, so the description should carry the burden of explaining what the agent will receive; it lists report themes but not structure, format, or the valid values for the 'rapport' parameter. An agent would still need additional knowledge to call this tool correctly for a specific report type.

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 only 67%: the required 'rapport' parameter has no description, and the tool description does not clarify its accepted values (e.g., navrank vs clickrank) or format. The description's mention of NavRank/ClickRank hints at the parameter but does not compensate for the gap.

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 names the resource (NavRank/ClickRank report) and specifies its contents: page priority, recommendations, ML scores, anomalies, and traffic drift computed on weekly stats. It is clear but does not explicitly contrast with the sibling listNavrankReports, leaving some differentiation to the name and GET path.

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?

No guidance is given on when to call this tool versus listNavrankReports or getSiteStats, and no prerequisites are mentioned. The only usage signal is implicit: the tool name and the GET endpoint indicate retrieval of a specific report.

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