gitflic_auth_bindings

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral detail not in the annotations or schema: results are sorted alphabetically by project. It says nothing about pagination, result size, or what an empty binding list looks like, so it is helpful 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?

Two short sentences, front-loaded with the resource and scope, then the ordering guarantee. No filler, no restatement of the title or the annotations.

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?

For a simple read-only list tool with no output schema and fully documented parameters, the description covers purpose, scope, and ordering adequately. It falls short only on guidance about alternative auth tools and on whether results are paginated, which an agent may need for large projects.

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 description coverage is 100% and both optional parameters (raw, fields) are fully documented in the schema, so the baseline of 3 applies. The description's note that the list is complete ('all current') gives the agent confidence that filtering is not done server-side and that 'fields' is the only narrowing mechanism, adding a small amount of meaning.

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 ('List all current project → account bindings') and adds the ordering ('Sorted alphabetically by project'), so the agent knows exactly what comes back. It does not, however, differentiate itself from close siblings such as gitflic_auth_list or gitflic_auth_bind, which remain ambiguous without opening their schemas.

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?

There is no explicit when-to-use statement, no exclusion of alternatives (e.g. 'use gitflic_auth_bind to create a binding'), and no mention of prerequisites such as being authenticated. The read-only listing intent is only implied by the verb 'List'.

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