get_community_spaces

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

Goes well beyond the readOnlyHint annotation by disclosing auth injection, throttling under LearnWorlds' 30-per-10s cap, retry behavior on 429/5xx, and the exact error surfacing semantics for 401/403/404/422. This is rich behavioral context an agent would otherwise not know.

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?

Organized into labeled sections (Behavior, Parameters, Returns, Use when) with front-loaded purpose. Every sentence contributes useful information and there is no filler or repetition of schema content.

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?

Comprehensive for a read-only list tool with no output schema: it covers scope, ordering, pagination, auth, throttling, retries, status/error behavior, and usage guidance. Nothing essential is missing for correct invocation.

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 100%, so the baseline is 3. The description adds meaningful procedural guidance on pagination: 'walk them with page and size each page with items_per_page,' which is not obvious from the schema alone. This small extra semantic justifies a 4.

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 community spaces. Returns a list with all community spaces of the school.' The plural 'spaces' plus 'all' distinguishes it from the singular sibling get_community_space, and the sorting detail adds concrete scope. The endpoint is also included.

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?

Explicitly says 'Use when: safe to call speculatively for lookups and reporting' and 'Not for changing anything — use the matching 🟡 write tool.' It also lists the related Community tools, giving the agent concrete alternatives for different operations.

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