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

Adds real context beyond annotations: identity is always via sessionToken, and claim_mission only submits for owner review — Sinapses credit lands only on approval, never auto-credited. This clarifies the mutation semantics that readOnlyHint=false alone cannot convey. Doesn't cover rate limits or failure modes.

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 domain and identity rule, then sub-actions, then the critical no-auto-credit caveat, then the flow recap. Dense but every sentence carries information; only the final flow line partly repeats earlier 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?

With no output schema, the description carries return-value burden and does it well — titles, module/lesson counts, per-challenge status enum, reward, action link. What's missing is what claim_mission returns and any error/validation behavior.

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 already 75%, but the description adds provenance the schema lacks: slug comes from 'list', missionId comes from 'list_challenges', and proofText is what the owner will review. That cross-references the workflow, not just restating field types.

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 the resource (Trilhas/cursos and Desafios/missões da Sapiens) and enumerates the four sub-actions with what each returns. An agent can distinguish this from all 28 sibling tools 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?

Explicit flow guidance: 'list → get' and 'list_challenges → claim_mission', plus where each ID originates. No explicit when-not or named alternative, but no sibling overlaps the courses/challenges domain, so the guidance is essentially complete.

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