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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds a genuine behavioral nuance beyond that: for get_growth, membershipId is optional because participants always see their own record, which is authorization context the annotations do not provide. Return format and pagination behavior are left unstated.

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?

A single dense sentence front-loads the verb and then enumerates modes in order of increasing specificity. Every clause earns its place, though the parenthetical chain makes it slightly list-heavy rather than crisply segmented.

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 still covers every action's required and optional inputs plus the get_growth authorization nuance, which is enough for correct invocation. It omits what each mode returns and whether list results paginate, a minor gap for a read tool.

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%, so the description must carry the load, and it does map all six parameters to their modes: action, query (required for search), category/status (list filters), membershipId (get_growth, optional), and matchId (required for get_match_skills). It does not restate enum values or UUID formats, but the schema already supplies those.

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 opens with a specific verb+resource ("Read skills") and enumerates the four read modes, so an agent can immediately tell this apart from the write-side sibling skills_manage. It stops short of naming any sibling explicitly, which keeps it at 4 rather than 5.

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?

Each action is paired with its selection condition and prerequisites — "search" requires query, "get_match_skills" requires matchId, "list" takes optional filters — which is strong when-to-use routing within the tool. It gives no when-not guidance and does not name alternatives such as skills_manage, so it is clear context without exclusions.

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