Bridge and project status

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered by structured data. The description's contribution beyond that is the inventory of returned state, which tells the agent this is a pure inspection call with no side effects implied. It adds no further behavioral context such as freshness of the reported state or cost of the call.

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?

One dense enumeration sentence plus a three-word directive, with no filler. The main structural weakness is that the most important instruction, 'Call this first', is buried at the end rather than front-loaded where it would drive tool selection immediately.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does so item by item across plugin state, folders, project contents and open tabs. For a zero-param inspection tool this is close to complete, missing only detail about how the tab edit counts or folder lists are formatted.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is an empty object with full coverage, consistent with the description's no-argument framing.

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 enumerates exactly what the tool surfaces: GeckoLib plugin presence, allowed output/asset folders, the open project's format, bones, cubes, textures and animations (plus display transforms for Java models), and every open tab with its edit count. That is specific enough to distinguish it from siblings like ping or open_model. It lacks an explicit verb up front ('reports'/'returns'), so the purpose is inferred from the content list rather than stated.

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?

'Call this first' gives a clear, actionable ordering directive that an agent can follow without inference. It does not name alternatives or say when not to call it, but for a zero-parameter state-inspection tool there is little ambiguity about alternatives.

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