github_gitignore_get_all_templates

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

No annotations are provided, so the description carries the full burden. 'Get all gitignore templates' is minimal and lacks details about authentication, rate limits, or the nature of the return value. However, for a simple read-only list operation, it is minimally adequate.

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, front-loaded sentence of four words. It contains no unnecessary words and efficiently conveys the tool's purpose.

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's simplicity (no parameters, no output schema), the description is functionally complete. It adequately informs the agent that the tool retrieves a list of all gitignore templates. While it could mention that the result is a list, it is largely sufficient.

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?

There are zero parameters, and the input schema has 100% documentation coverage. According to the rubric, 0 parameters earns a baseline of 4. The description does not need to add parameter-specific information.

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 'Get all gitignore templates' clearly states the verb 'Get' and the resource 'all gitignore templates'. It effectively distinguishes itself from the sibling tool 'github_gitignore_get_template' by using 'all', making the purpose unambiguous.

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 that this tool should be used when all templates are needed, as opposed to the sibling tool for a specific template. While not explicitly stating when not to use it, the context of 'all' versus 'get_template' provides clear guidance.

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