gitee_get_license_raw

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

The description does not disclose any behavioral traits. With no annotations, it fails to mention permissions, rate limits, error handling, or return format. The agent knows nothing about what happens if the license key is invalid or how the raw text is returned.

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 extremely concise at one sentence with no filler. However, it is almost too terse; a bit more detail would improve clarity without sacrificing conciseness. It is not wasteful but could be more informative.

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 simple tool (1 param, no nested objects, no output schema), the description is partially complete. It mentions the purpose but omits output details, error scenarios, or usage context. The absence of an output schema means the description should hint at return value, which it does not.

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 describes 'license' as 'License key', and the description merely restates the parameter name. No additional meaning is added, such as where to find valid license keys, expected format, or examples. With 100% schema coverage, the description should enhance understanding but falls short.

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 verb 'get' and the resource 'raw license text', indicating what the tool does. However, it does not differentiate from sibling tools like gitee_get_license or gitee_get_repo_license, which might retrieve structured license data or per-repo licenses. The term 'raw' is vague and could be clarified.

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?

No guidance is provided on when to use this tool versus alternatives such as gitee_get_license or gitee_get_repo_license. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage without support.

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