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

Annotations already declare readOnly/non-destructive, so the description correctly spends its words on what the read returns: full entry/panel coverage and the guarded isProtected flag. It also explains the speechLanguage / languageVariants data shape, which is real behavioral context the agent could not infer from the schema. No pagination or size caveats, though.

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?

Leads with the core read scope and the key usage instruction, then adds the language-variant detail where it belongs. Slightly dense in the parenthetical example, but 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?

With no output schema, the description has to sketch the return shape, and it does: entries, panels, panel content, isProtected, plus the language tabs structure. Only missing piece is any sense of response size or completeness guarantees for large scenarios.

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?

Single parameter with 100% schema description coverage; the schema already tells the agent projectId comes from list_scenarios. The description adds nothing about the parameter, so 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 and resource with scope: reads *every* entry and panel of a scenario, including panel content and the isProtected flag. This implicitly separates it from narrower readers like search_entries or get_world, though it never names a sibling explicitly.

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?

'Start here before writing' gives a clear sequencing rule that an agent can act on. It stops short of naming alternatives (e.g. use search_entries for lookups) or stating when not to use it.

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