get_site_stats

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

Annotations already provide readOnlyHint=true, indicating safe read-only operation. The description adds that it returns totals of datasets, organizations, groups, and tags, which is the core behavioral output. However, there is no additional disclosure beyond the annotations (e.g., rate limits, data freshness). Score 3 is appropriate as annotations cover safety and description adds return value context.

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, front-loaded with the portal name, and conveys all necessary information without any fluff. Every word earns its place.

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 the absence of parameters and output schema, the description is complete. It clearly states what the tool returns (total datasets, organizations, groups, tags). No additional information is necessary for a simple stat 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?

There are zero parameters, so schema coverage is 100% and the description need not add parameter semantics. Baseline for zero parameters is 4. The description does not need to compensate.

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 returns general statistics (total datasets, organizations, groups, tags) of the portal datos.gob.do. The verb 'Devuelve' (returns) and resource 'estadísticas generales' are specific. It distinguishes from siblings like get_dataset or get_organization which focus on individual entities.

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 high-level portal statistics. It does not explicitly state when not to use or name alternatives, but the sibling list includes specific tools for datasets, organizations, etc., making the tool's context clear. A slightly higher score would require explicit guidance.

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