pob_tree_textures

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

readOnlyHint=true is consistent with a texture-retrieval operation, so the safety profile needs no restating. The description adds the output format (PNG RGBA), but says nothing about token lifetime, failure behavior for an invalid or expired token, or how the image is delivered.

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 with zero filler: the first states the product, the second states exactly where the input comes from. Front-loaded and easy to parse.

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 single-parameter, read-only image tool this is nearly sufficient, and the cross-tool token provenance is the key missing piece that the description supplies. Minor gaps remain around token expiry and return shape, though the output format is stated.

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 0%, so the description must carry the parameter's meaning, and it does: 'token' is defined by provenance (scene.commands[].texture from pob_get_tree with includeScene=true). The 64-character limit and string format remain undocumented, but the essential semantics are covered.

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?

Names the concrete resource produced (a finished PoB scene texture as PNG RGBA), so the agent knows what it is getting. There is no explicit verb (return/fetch/export) and nothing distinguishes it from the sibling pob_render_image, which an agent could easily confuse it with.

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?

Explicitly tells the agent the prerequisite for use: obtain the token from scene.commands[].texture via pob_get_tree(includeScene=true). That is real, actionable when/how-to-use guidance. It does not say when to prefer this over sibling image tools such as pob_render_image or pob_tree_icons.

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