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

With only readOnlyHint=true declared, the description carries most of the burden and does add real behavioral context: the data comes from Reddit and other monitored communities, it reflects recent activity, it is aggregated per community, and the underlying requests are restricted to TutorPing tutors. It does not state how far back "recently" reaches or how counts are computed, but the access-policy and data-source disclosures are valuable beyond the annotation.

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?

Three sentences, front-loaded with the core measurement and followed by use case and access policy, with no filler. Slightly more compact phrasing could merge the second and third sentences, but each sentence contributes distinct information.

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 read-only, two-parameter tool with no output schema, the description covers what is measured, the source, the aggregation level (by community), and the access restriction. The main remaining gap is the unspecified time window, which the agent must infer from the days parameter and its default.

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 only 50%: the subject parameter is documented in the schema ("SAT", "organic chemistry", "piano"), but days has no schema description. The description's "recently" loosely gestures at a time window but never mentions the days parameter, its default of 7, or its 14-day cap, so it does not compensate for the coverage gap.

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 states a specific measurement (how many people recently asked for a tutor) applied to a specific scope (a subject), with an explicit data provenance (Reddit and other communities TutorPing monitors). It is clearly distinguishable from the sibling tools (get_tutor, search_tutors, request_booking), which all deal with tutors/bookings rather than aggregate demand, though it never names a sibling to contrast against.

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?

"Useful for tutors deciding whether there is demand for their subject" gives an intended audience and a decision context, which is more than a bare purpose statement. However, there is no explicit when-to-use/when-not guidance and no alternative tool is suggested for related needs, so the usage framing stays implicit.

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