aestheticspro_read

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

With no annotations, the description carries the full burden. "Read" implies a non-mutating operation and the sentence discloses the shape of the returned content (text, numbered buttons, links, fields), which is genuinely useful since there is no output schema. However, it says nothing about truncation, page-size limits, or whether reading has any side effects on the session.

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?

One sentence, front-loaded with the verb and resource, with zero filler. It is efficient but borders on terse given the missing operational detail.

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 simple read tool with no output schema this is adequate, but it omits a critical workflow detail: whether the "numbered" buttons and fields are the identifiers the agent should pass to aestheticspro_click and aestheticspro_type. It also never connects the optional element parameter to the numbering, which an agent needs to act correctly.

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 100% and the single optional parameter is documented as "Read only inside this element," so the baseline of 3 applies. The description does not mention scoping to an element at all, adding no meaning beyond the schema.

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?

"Read the current AestheticsPro page" gives a specific verb plus resource, and the enumeration of text, numbered buttons, links and fields tells the agent what kind of content comes back. It is clearly distinct from the mutating siblings (click, type, open, close), though it does not explicitly distinguish itself from status or guide.

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: an agent can infer this is the way to inspect page state, likely after a click or type. There is no explicit statement of when to prefer this over aestheticspro_status or aestheticspro_guide, and no mention of the typical read-then-act loop.

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