assess_league_readiness

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

No annotations are provided, so the description must fully disclose behavioral traits. It states that the tool queries 'live Supabase data' and computes scores, implying a non-destructive read operation. However, it does not explicitly declare read-only behavior, idempotency, or potential side effects. The listing of dimensions is informative but not sufficient for full transparency.

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?

The description is reasonably concise with a clear purpose statement upfront. It uses a bulleted list for dimensions, which improves readability. However, it could be slightly more streamlined by removing redundant phrase 'using live Supabase data' if context is obvious.

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?

Given the tool has an output schema (context signal), the description adequately summarizes return values without needing full details. It covers the key components: overall score, certification eligibility, per-dimension breakdowns, and recommendations. Missing error handling or prerequisite conditions, but acceptable for a tool with simple parameters and existing output schema.

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 100%, so the baseline is 3. The description adds no significant meaning beyond what is already in the input schema. For instance, the default value and description of 'assessment_type' are already present in the schema. The description does not introduce new constraints or clarifications.

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 clearly states the tool assesses a league's readiness using live data and lists five specific dimensions with weights. It outlines the return values (overall score, eligibility, breakdowns, recommendations). However, it does not explicitly differentiate from sibling tools like 'evaluate_league' or 'rank_league_maturity', which have overlapping purposes.

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 implies usage for readiness assessment but provides no explicit guidance on when to use this tool versus alternatives. There are no when-not-to-use statements or exclusions. Without such context, an agent may struggle to choose among related sibling tools.

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