Get the raw content of a theme CSS/JS asset

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

With no annotations, the description carries the full burden. It usefully discloses the server-side SSRF guard and the wp-mcp-bridge/v1 REST route, but says nothing about the response shape beyond 'raw text', authentication requirements, size limits, or error behavior (e.g. what happens if the URL is off-host).

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, front-loaded with the verb and resource. The REST-route detail is mildly technical but plausibly useful context; no filler sentences.

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 tool with no output schema, the description covers what is fetched, where the URL comes from, and the host constraint. It does not explain the return format or failure modes, but the essentials an agent needs to call it correctly are present.

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 100%, so the baseline would be 3, but the description adds genuine meaning: the URL must originate from get_theme_styles and must be same-host, a constraint not encoded in the schema format/description.

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 (Fetch) and resource (raw text content of a CSS/JS asset URL), and explicitly ties the URL provenance to the sibling tool get_theme_styles. An agent can distinguish this from get_theme_styles and the page tools without opening any 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?

It clearly establishes the context of use: the URL must come from get_theme_styles and must be on the connected site's host. It does not state explicit exclusions or alternatives, but the prerequisite and constraint give strong routing guidance.

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