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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description doesn't need to restate those. It adds 'bounded' implying a limit parameter, but does not describe pagination, sorting, or other behavioral nuances. This is adequate but not rich.

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 extraneous details. It front-loads the return object and then states the purpose, making it concise and well-structured.

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?

Given there is no output schema, the description lists the metrics returned, which is helpful. However, it does not mention sorting, limit behavior, or how to interpret the metrics, and it omits guidance on segment or period usage. It is sufficient for a basic call but leaves room for interpretation.

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 71%, and the description adds minimal value beyond the schema. It hints at the limit via 'bounded' but does not explain how to use period, segment, or limit effectively. The description does not compensate for the missing parameter details.

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 a verb ('Return'), a resource ('Matomo page URLs'), and lists the exact metrics (views, unique views, entrances, exits, bounce rate, time on page). It also explains the analytical purpose ('which content attracts, engages, or loses visitors'), which distinguishes it from siblings like matomo_goal_performance and matomo_visit_summary.

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 implies usage for content performance analysis via the purpose statement, but it does not explicitly mention when to use this tool versus alternatives or when not to use it. An agent must infer the appropriate context from the phrasing.

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