kaggle_get_competition

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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds that it fetches details and a truncated rules digest, and explicitly states 'Read-only.' This aligns with annotations and provides additional behavioral context beyond what annotations offer.

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 a single succinct sentence with no redundant words. It front-loads the action and result, and the clarification about the slug is efficient.

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 a single required parameter and an output schema is present (not shown but indicated), the description adequately covers what the tool does and what it returns at a high level. It could mention the output schema details, but not required.

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 0%, but the description compensates by explaining the parameter: 'competition' is the bare slug (e.g., 'titanic'). This adds crucial format and example information that the schema lacks, helping the agent form the correct slug.

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?

Description clearly states 'Fetch one competition's details and a truncated, untrusted-wrapped rules digest.' This specifies the verb (Fetch), resource (competition), and distinguishes from sibling tools like kaggle_list_competitions which lists all competitions.

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 a single competition by emphasizing the bare slug parameter, but it does not explicitly state when to use this tool versus alternatives like kaggle_list_competitions or kaggle_competition_leaderboard.

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