speechwire_get_judge_availability

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

No annotations are provided, so the description bears the burden. It discloses the return format (list of dicts with specific fields) but does not mention whether the operation is read-only, rate limits, error behavior, or prerequisites beyond the ID source.

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 concise and well-structured with separate 'Parameters' and 'Returns' sections, using bullet points for clarity. Every sentence earns its place without redundancy.

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's simplicity (one required parameter, output schema available), the description adequately covers input, parameter origin, and output structure. It fully addresses the agent's needs for 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?

The description adds meaningful context beyond the schema: it specifies that judge_id is a 'Numeric judge identifier from speechwire_list_judges', which tells the agent how to obtain the correct value. Schema coverage is 0% otherwise.

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 'Get a judge's availability by timeslot' using a specific verb and resource. Among siblings, there is 'speechwire_update_judge_availability' which is different, so the purpose is well-differentiated.

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 identifies the source of the judge_id ('from speechwire_list_judges'), which implies a prerequisite. However, it does not explicitly state when to use this tool over siblings or what contexts to avoid (e.g., for updating availability).

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