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

Annotations already cover the safety profile (readOnly, non-destructive, not open-world), so the bar is lower; the description still adds real behavior: the result is ordered upcoming-soonest-first, capped at 50 upcoming then 12 newest past, and 404s for organizers without a display name. It does not discuss any further pagination or rate limits, but for a read-only fetch this is solid.

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?

Front-loaded with the purpose, then the return composition, then the failure condition, in compact sentences with no filler. Every clause (fields, ordering, caps, 404) 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?

With no output schema, the description does the work of describing the return shape—profile fields plus the ordered, capped event lists—and the failure mode, which is thorough for a simple read tool. The only gap is the unexplained slug input, which is the sole required argument.

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 is a single parameter (slug) with 0% schema description coverage, so the description carries the burden—yet it never explains what 'slug' is, its format, or how to obtain it. It implies the page is looked up by organizer but adds no semantics beyond that implication.

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?

States a specific verb and resource ('Get an organizer's public page') and immediately enumerates the page's contents (name, About, website, town/state, crafts, picture) plus the events it carries. The resource is unique among the siblings (all of which are event/site oriented), so an agent can place it without opening the schema.

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 gives one useful precondition (only organizers with a display name have a public page; otherwise 404) but offers no explicit when-to-use-vs-alternatives guidance and names no sibling. Usage is implied by the trigger condition rather than stated.

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