superpos_get_track

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

No annotations are provided, so the description carries the burden. It discloses that issues are included 'by default', hinting at the 'include_issues' parameter default. However, it does not mention any side effects, authentication requirements, or rate limits. The information is adequate but not rich.

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 sentence that front-loads the main action and key included data. Every word is necessary; no fluff.

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 (so return values are documented there), the description provides a useful summary. For a simple retrieval tool, it is mostly complete, though it could mention that the result is a single track object.

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%, so the description must compensate. It indirectly explains 'slug' (identifies the track) and 'include_issues' (included by default), but does not mention 'hive_id' at all. Two of three parameters get partial explanation, leaving a gap.

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 action ('Get'), the resource ('track by slug'), and what is included ('full spec document and...issues linked to it'). It distinguishes from siblings like 'list_tracks' (which lists all tracks) and 'get_issue' (which gets a single issue).

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 when a specific track slug is known and one wants the full spec and issues. However, it does not provide explicit guidance on when not to use it or mention alternatives such as 'list_tracks' for browsing or 'get_issue' for issue details.

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