streamdeck_read_page

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

The description indicates the tool is a read-only operation ('Read'), which is a basic behavioral disclosure. Since no annotations are provided, the description carries full burden but does not elaborate on error behavior, idempotency, or consequences of providing multiple optional parameters.

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?

The description is a single sentence with no unnecessary words. It efficiently conveys the core purpose and parameter relationships.

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?

The tool has no output schema, so the description should explain what the tool returns. It does not. Additionally, with four optional parameters, there is no guidance on how they interact (e.g., whether profile_name or profile_id is required, or if both must be provided).

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 input schema has 100% description coverage, so the baseline is 3. The description adds minimal extra meaning by framing the parameters as alternatives, but the schema already provides clear descriptions for each parameter.

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?

The description clearly states the verb 'Read' and the resource 'profile page'. However, it does not distinguish this tool from the sibling 'streamdeck_read_profiles', which reads all profiles. The description could explicitly mention that this tool targets a specific page, not the entire profile.

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?

No guidance is provided on when to use this tool versus its siblings like 'streamdeck_read_profiles' or 'streamdeck_write_page'. The description merely lists parameters without contextual advice.

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