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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond annotations by specifying pagination, metadata-only results, and project scoping, which helps an agent understand what to expect from the call.

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, focused sentence with no filler. It front-loads the action and resource, and every word adds meaning.

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-only list operation with an output schema and safety annotations, the description is mostly complete. It captures pagination, metadata scope, and project context. It could be slightly more explicit about how this relates to sibling tools, but that is more of a usage-guidelines gap than a completeness gap.

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?

With schema description coverage at 0%, the description must compensate for missing parameter explanations. It only hints at pagination and the Growth project scope; it never explicitly explains that project_id is the required project identifier or how limit and offset drive pagination. This leaves most parameter semantics under-specified.

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 uses a specific verb ('Read'), a clear resource ('saved scenario metadata'), and scope ('in a Growth project'), which differentiates it from single-scenario retrieval tools like sparkclose.get_scenario and write tools like sparkclose.save_scenario. The title 'List SAFE scenarios' aligns with the description, though 'Growth project' is not further defined.

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 description clearly implies when to use the tool: to read paginated scenario metadata for a project. It does not explicitly state alternatives or when not to use it, but for a simple list operation the context is clear enough.

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