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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds a behavioral detail: it does not extend the visit. This is useful context beyond annotations, but it is brief and does not elaborate on potential side effects or auth requirements. The addition is modest, fitting a score of 3 given annotation coverage.

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 sentences, front-loaded with the key relationship ('Alias for rest') and a concise behavioral note. No wasted words; every sentence carries information.

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 description is very short and omits explanation of the 'host' parameter, what a 'scene' is, or what to expect when reading. While annotations cover safety, the lack of parameter and outcome detail leaves an agent with insufficient context to call the tool confidently without prior knowledge of 'rest'.

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 description mentions no parameters. With schema description coverage at 50%, the session parameter is documented but the host parameter is not. The description does not compensate for this gap or add meaning beyond the schema, so parameter semantics are poorly served.

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 states it is an alias for 'rest' and that it reads another scene without extending the visit. The verb 'read' is clear, but the resource 'scene' is undefined, leaving the exact purpose vague. It does differentiate from other siblings by referencing 'rest', but without knowing what 'rest' does, the purpose remains somewhat opaque.

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 phrase 'without extending the visit' implies a usage condition, but there is no explicit guidance on when to use this tool versus 'rest' or other alternatives. No prerequisites or exclusions are stated, leaving the agent to infer from the alias relationship.

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