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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful piece of context beyond that: the returned data is restricted to metadata/approved fields with no secrets, contacts, or original files. It still says nothing about pagination behavior, result volume, or authorization requirements.

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?

Two short sentences with the operation stated first and the data-scope constraint second; nothing is padded. The only waste is the empty phrase "through the existing application".

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?

With no output schema and no documented parameters, the description carries a heavy burden and does not meet it: an agent cannot tell what the analytics contain, how results are paged, or how "query" is interpreted. The data-boundary sentence helps but does not compensate for the missing operational detail.

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?

Three parameters (limit, offset, query) exist with 0% schema description coverage, and the description mentions none of them. Nothing explains what "query" filters over, whether offset paging is supported, or what the default page size means for the caller.

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?

"Read authorised course performance analytics" gives a verb and a resource, but the scope is hedged and vague ("authorised", "through the existing application"). It never says what performance dimensions are returned, and it does not distinguish itself from analytics siblings such as get_analytics_kpis, get_dashboard_analytics, or get_location_compliance_analytics.

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?

There is no statement of when to use this tool versus the many other analytics tools in the sibling list, and no prerequisites or exclusions. The only guidance is a data-scope caveat, not a usage rule.

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