get_brief

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

No annotations are provided, so the description carries the full burden. It does disclose the payload contents (metric, deadlines, limits, submission format, external-data rule), which implies a safe read, but it says nothing about auth needs, competition-argument resolution, or any side effects. Adequate but thin for a zero-annotation tool.

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?

It is one compact sentence with the payload listed up front, so it is not bloated. However it is a sentence fragment whose trailing clause 'and what else is available' is vague and does little work, capping the value of its brevity.

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?

An output schema exists, so return values need not be described and the enumerated contents largely cover the response. Still, for a discovery tool in a crowded sibling set, the description leaves the core question — what this brief is for and how it differs from fetch_competition — unanswered.

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% and the single 'competition' parameter is unmentioned in the description. Its accepted form (slug, ID, numeric key) and the meaning of the nullable default — i.e., what happens when it is omitted — are not clarified anywhere.

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 names the contents returned (metric, deadlines, limits, submission format, external-data rule) but gives no verb and never states the resource — that this is a brief/summary for a competition. Against siblings like fetch_competition and get_section, an agent cannot tell from the text why or when it would pick get_brief over them.

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?

There is only the vague tail 'what else is available' to suggest this is a discovery/orientation entry point. No explicit when-to-use, when-not-to-use, or alternatives are named, so routing between get_brief, fetch_competition, and get_section is left entirely to inference.

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