get_ontology_analytics

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

With no annotations, the description must disclose behavior fully. It describes that it retrieves analytics data but does not mention authentication, rate limits, or side effects. However, the tool is read-only and the API key parameter is in the schema, so basic transparency is adequate.

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 two sentences with no redundant words. The first sentence states the purpose, and the second elaborates on usage, making it front-loaded and efficient.

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?

The description covers the main functionalities: retrieving analytics for all or specific ontologies with optional time filters. An output schema exists, so return values are documented separately. No missing critical aspects for this simple tool.

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 coverage is 100%, so the baseline is 3. The description summarizes parameter usage (filter by month/year, specific ontology) but adds no new details beyond the schema descriptions. Thus, it does not exceed the baseline.

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 states it gets visitor analytics for BioPortal ontologies. It specifies three modes: all ontologies, filtered by month/year, or for a specific ontology. This distinguishes it from sibling tools which search properties and terms.

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 clear usage context: it can retrieve analytics for all ontologies, filter by month/year, or get detailed analytics for a specific ontology. However, it does not explicitly state when not to use it or compare with alternatives, though the alternatives are unrelated.

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