show_competition_topic

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

With no annotations available, the description carries the full burden of disclosure, but it only says 'Show'. It does not state whether this is a read-only operation, what the response contains, what topic_ref identifies, or how failures are surfaced.

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 short and front-loaded, but it is under-specified rather than efficiently complete. A second sentence could have clarified the topic_ref format or return value without harming conciseness.

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?

For a tool with zero parameter documentation, no output schema, and no annotation context, the description is materially incomplete. It does not say how to obtain a valid topic_ref, what the tool returns, or how this relates to the competition topic listing workflow.

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 schema has one required parameter, topic_ref, with an empty description and 0% schema coverage. The tool description adds no explanation of how to format or resolve topic_ref, leaving the agent without the information needed to populate it correctly.

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 states a clear action ('show') and resource ('competition topic thread'), and the 'competition' scoping distinguishes it from show_kernel_topic, show_dataset_topic, and show_forum_topic. The term 'thread' is slightly ambiguous relative to 'topic', but the core purpose is recognizable.

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 no guidance about when to use this tool versus list_competition_topics or the other show_*_topic siblings. An agent must infer the intended usage entirely from the tool name and a single verb phrase.

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