Simulation Data

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds pagination behavior, which is useful but does not elaborate on other aspects like rate limits or error handling. No contradictions with annotations.

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 two sentences: the first lists all data types concisely, the second provides pagination guidance. It is front-loaded, efficient, and every word earned its place.

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?

Given the 7 parameters and no output schema, the description covers the tool's purpose and pagination well. It lacks details on return format or error handling, but for a data-access tool with comprehensive schema descriptions, it is largely complete.

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 description coverage is 100%, with each parameter well-described. The tool description adds minimal parameter-level insight beyond the schema (e.g., pagination hint for offset). Thus, the description provides little extra value for parameter semantics.

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 tool accesses simulation data and enumerates all data types (profiles, config, actions, posts, timeline, etc.). This specificity distinguishes it from sibling tools like cancel_simulation or create_simulation, making the purpose unmistakable.

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 mentions pagination but does not explicitly guide when to use this tool versus alternatives. It implies it's the read-only data retrieval tool among siblings, but lacks explicit 'when-not-to-use' or references to other tools.

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