blender_quality_guidelines

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds that the content is served from the server's own copy rather than the addon, which usefully tells the agent the response is real content rather than the old placeholder. It does not describe filtering or output shape beyond the schema.

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?

Purpose is front-loaded and the content overview is useful, but the final two sentences are largely historical narrative about the addon-package resolution bug. That provenance detail is interesting but occupies roughly a third of the text without helping an agent decide or invoke.

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-required-param, read-only fetch with full annotation coverage and no output schema, the description is close to sufficient: it says what is returned and why it is trustworthy. It omits only the return format/pagination implications of the parameters, which the schema partially covers.

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 description adds nothing about the three parameters; 'wheels'/'realism' filtering, the limit, and the markdown/json choice are only in the schema. Schema coverage is a moderate 67% (limit and query have no descriptions), so the description neither compensates for the gap nor does real harm – baseline territory.

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?

States a specific verb and resource: 'Fetch the modelling quality guidelines the agent should follow.' The content summary (proportions, structure, camera/lighting, texture resolution) makes its scope concrete and it is clearly unlike any sibling. It stops short of naming an alternative, but nothing else in the toolset serves this resource.

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?

Usage is only implied by 'the guidelines the agent should follow' and by references to 'before a render' and 'a close-up.' There is no explicit statement of when to invoke it versus related verification tools (e.g. blender_validate, blender_auto_validate) or whether it should be consulted before generating a model. Adequate but leaves sequencing to inference.

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