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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds behavior beyond that: 'Every GitHub project works with UGT, so the result always says what to do next' — telling the agent there is no unknown-project failure path and that responses carry next-step guidance. It does not discuss latency, caching, or what happens for private or nonexistent repos, which would have pushed this higher.

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?

Three short sentences, front-loaded with the verb and resource before the call trigger. Minor waste in promotional phrasing like 'each verified for one job' and 'what to do next', but nothing is padded to the point of obscuring the point.

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 no explanation, and the description still usefully characterizes the response as always containing next steps. For a single-parameter, read-only lookup the definition covers purpose, input format, and invocation trigger adequately; only sibling routing is left implicit.

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 100% and the single 'project' parameter is fully documented in the schema as owner/repo or a GitHub link. The description repeats the same accepted formats without adding syntax, normalization, or edge-case guidance, so the schema does the work and baseline 3 applies.

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 gives a specific verb and resource: 'Get how UGT runs one GitHub project ... the recipes people have shared for it.' The 'recipes' framing implicitly separates it from get_recipe (single recipe) and search_recipes (discovery), but it never names those siblings, so the differentiation is inferential rather than explicit.

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?

It states a clear trigger: 'Call it whenever the user names a GitHub project they want to use.' That is a usable when-to-use rule. It stops short of naming alternatives (get_recipe, search_recipes) or stating when not to use it, so an agent must still infer the routing for a named recipe versus a named project.

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