util_star_repo

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

The description mentions behavioral traits: it uses GitHub CLI if available, else opens a browser. This provides some transparency about execution. However, it does not disclose potential side effects, authentication requirements, rate limits, or whether the action is idempotent. Without annotations, more detail is needed.

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: two sentences with no wasted words. It front-loads the purpose and then adds implementation detail. Every sentence earns its place.

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?

The tool is simple with no parameters, so the description is mostly complete but lacks context about which repository is starred (potentially the current context) and prerequisites (e.g., need a GitHub account). It could mention that the repository is determined by the current page or command context.

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 input schema has 0 parameters, so the description adds meaning by explaining the tool's behavior (CLI vs browser). With no parameters, baseline is 4, and the description meets that by clarifying the action.

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 tool's purpose: starring a GitHub repository. It uses a specific verb 'Star' and a specific resource 'GitHub repository', which distinguishes it from sibling tools that are focused on SEO analytics and site management.

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 the user wants to support a GitHub project, but it does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. No guidance on prerequisites or context is given.

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