List JsonFabrica generator function weights (admin)

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

With no annotations, the description carries the behavioral burden. It discloses the HTTP method, the admin requirement, and the 403 failure mode, which is useful. However, it does not describe the success response contents, pagination, or any read-only guarantee beyond the GET verb.

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 tight sentences with no filler. The endpoint is front-loaded and the auth caveat is immediately useful. Every word earns its place.

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 zero-parameter GET endpoint, the description covers the call target, the required auth role, and the error condition. The only notable omission is an explicit statement of the successful response format, but the title and endpoint strongly imply a list of weights.

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 has zero parameters, so the schema fully covers everything. The baseline of 4 applies because there is no parameter meaning to convey and nothing to compensate for.

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 names a specific verb and resource: 'Calls GET /v1/admin/function-weights' and the title states 'List JsonFabrica generator function weights'. This unambiguously differentiates it from sibling update_function_weight and other list tools.

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 admin-role prerequisite is clearly stated, but there is no explicit guidance on when to choose this over alternatives. Usage is implied from the name and endpoint, but no when/when-not or alternative tool references are provided.

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