foundry_get_current_client

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

Annotations provide readOnlyHint=true, which already discloses the read-only nature. The description adds context about the 'currently resolved' state and the relationship between scoped keys and clientId, which goes beyond the annotation without contradicting it.

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, both of which earn their place: the first states the primary action, and the second provides a key nuance about scoped keys. There is no filler or redundancy.

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 tool's simplicity (0 params, readOnly annotation), the description is fairly complete. It conveys the core purpose and a relevant edge case. It could be more explicit about the exact return value, but the mention of clientId implies the output sufficiently.

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 tool has no parameters, so the schema is fully covered. The description does not need to add parameter details, and the note about scoped keys gives contextual meaning that is helpful for understanding the tool's behavior.

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 action ('Get') and the resource ('the relay's currently resolved Foundry world'). It also adds the distinguishing detail about scoped keys and clientId, which helps differentiate this tool from siblings like foundry_list_clients.

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 'With a scoped key' gives a specific scenario for using the tool, and it explains the benefit (identifying clientId without FOUNDRY_CLIENT_ID). However, it does not explicitly name alternatives or state when not to use the tool, so it falls short of a 5.

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