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

With no annotations, the description carries the full disclosure burden. It does reveal the returned metrics (unique visits all time/this week, project views, weekly rank, last 14 days), which is useful behavioral context, but it omits access requirements, rate limits, return structure, and whether results are scoped by anything beyond the username.

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 with no filler. It is front-loaded with the returned metrics, though it could be more structurally organized around purpose and usage.

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?

For a one-parameter read-only-style stats tool with no output schema, the description does enough to list the key metrics. However, without annotations or an output schema, it should say more about return shape, limitations, and when the username-based stats are appropriate.

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 0% and the only parameter is 'handle.' The description partially compensates by indicating the handle identifies a username, but it does not specify format, constraints, or how the username is resolved.

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 specific metrics and says they are for one username, so an agent can infer it returns visit/project stats. However, it never states a clear verb or resource like 'retrieve user statistics,' and the title 'Visits of a building' conflicts with the username-focused description, making the intended target ambiguous.

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 guidance on when to use this tool instead of siblings such as get_profile, popular, live, or get_building. The only contextual hint is 'for one username,' which does not establish alternatives or exclusions.

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