streamelements_read

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

With no annotations, the description carries the full behavioral burden. It does useful work by disclosing the return contents (text, numbered buttons, links, fields), which tells the agent the page is presented as an indexed, actionable view. It does not say whether the read is passive, whether numbering is stable across calls, or whether large pages are truncated.

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 the target, with the payload listed after the colon. Nothing is wasted, though the compressed phrasing leaves helpful detail such as the numbering convention unstated.

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 one-parameter read tool with no output schema and no annotations, the description covers what comes back but not the conventions an agent needs — notably that the numbered buttons are the handles consumed by streamelements_click. Adequate but with a real gap for a browser-driving toolset.

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% and the single 'element' parameter is documented as 'Read only inside this element', so the schema does the work. The description says nothing about scoping or the meaning of element, so it adds no meaning beyond the schema — the baseline 3 applies.

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 a specific resource (the current StreamElements page), then enumerates what is returned: text, numbered buttons, links and fields. That goes well beyond the name, though it never names a sibling tool, so an agent must infer from the sibling list that this is the inspection half of a click/type workflow.

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: reading the page is obviously a precursor to streamelements_click and streamelements_type, but the description never says so, nor does it state when to prefer this over streamelements_status or streamelements_guide. No exclusions or prerequisites are given.

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