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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds the one behavioral note that the theme filter must match exactly, but says nothing about result size, ordering, or pagination. Given annotation coverage, this is adequate but thin.

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 tightly packed sentences with no filler: the scope of data read comes first, then the routing hints. Dense but front-loaded and free of redundancy.

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 read-only listing tool with no output schema and one parameter, the description compensates by enumerating the categories of data returned and noting the optional exact filter. An agent has enough to invoke it correctly, though ordering/pagination behavior is unaddressed.

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 coverage is 0% for the single 'theme' parameter, so the description carries the burden and does add the key semantic that the filter is 'optional' and must be an 'exact' match. It stops short of giving format examples or stating behavior for non-matching themes, so the gap is only partly closed.

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 (Read) and enumerates the concrete resources returned (native contracts, themes, units, assumptions, backends, approved composition families). It also explicitly distinguishes itself from the sibling list_composition_capabilities and from tools/list, so an agent can tell them apart without opening a schema.

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 second sentence gives comparative context ('tools/list discovers direct MCP tools; list_composition_capabilities adds planner bindings'), which implies where this tool sits. However, it never states when to choose this tool over those alternatives — no condition or task framing that selects it — so usage remains implied rather than explicit.

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