foundry_get_effects

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

The readOnlyHint annotation already signals a safe read operation, so the description's 'Get' aligns with it. However, the description adds no further behavioral context such as whether inherited effects are included, what happens if no effects exist, or whether permissions affect the result beyond the schema's userId hint.

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?

A single, short sentence that is immediately informative and free of any redundant or extraneous text.

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 getter with readOnlyHint and clear param semantics, the description is complete enough to guide invocation. It could note the return type, but the tool name and description already convey the core purpose adequately given the sibling context.

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 descriptions cover userId and clientId, but uuid lacks a description. The tool description clarifies that the uuid refers to an actor or token, providing necessary meaning for the required parameter. This compensates for the 67% schema coverage.

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 the specific verb 'Get' and identifies the resource ('active effects') and its target ('an actor or token'), clearly distinguishing it from mutation tools like foundry_add_effect/foundry_remove_effect and from foundry_list_status_effects which likely returns all status effects globally.

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 implies usage for retrieving active effects on a specific actor or token but provides no explicit guidance on when to prefer this over alternatives like foundry_get_entity or foundry_list_status_effects. No exclusions or alternatives are mentioned.

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