get_fbx_export_status

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description correctly reinforces with "No export or file writes." It adds real value beyond the annotations with "Method availability is not proof of a successful export," which warns the agent how to interpret a positive result. It stops short of describing the shape of the returned entitlement data.

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?

Three short sentences, each earning its place: purpose, non-mutating guarantee, and an interpretation caveat. The core purpose is front-loaded with no filler or repetition of the name.

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?

With no output schema, the description still names what is returned (entitlement and loader methods) and warns about interpreting that result, which covers the essential contract for this query tool. Return structure/format remains unspecified, but nothing critical to invoking it correctly is missing.

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; the baseline for a parameterless tool applies. No parameter-related gaps exist.

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?

Specific verb ("Read") plus a concrete resource ("current native FBX export entitlement and loader methods"), so the agent knows this is a capability/status query rather than an action. It only implicitly contrasts with the sibling export_fbx via "No export or file writes," so a 4 rather than a 5.

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 export or file writes" implies this is the pre-flight check to run instead of export_fbx when you only want to know whether exporting is possible. However, it never states when to call it versus export_fbx or get_bridge_capabilities, and there is no explicit when-not guidance, leaving usage inferred.

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