symbols-of-wealth-studio

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

With no annotations provided, the description does a good job of indicating the read-only, informational nature of the tool by using 'Returns.' It clarifies the scope of the data (email, website, location, engagement) and the intended use case, giving the agent a clear sense of what to expect. It does not explicitly mention error cases or privacy, but for a simple contact-info getter, this is adequately transparent.

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?

Two sentences with no redundant words. The first sentence states the action and content; the second provides usage context. Perfectly concise and front-loaded.

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 tool with no parameters and no output schema, the description fully covers the purpose, the exact data returned, and the usage context. It also provides enough contrast with the sibling to avoid ambiguity. No further information is needed.

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 zero parameters, so the baseline is 4. The description doesn't need to explain any parameters, and it doesn't try to invent any, which is appropriate.

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 'Returns' and explicitly identifies the resource as 'contact information for Symbols of Wealth Studio,' listing the exact fields (email, website, location, how to engage). It also distinguishes itself from the sibling tool by contrasting with browsing the full studio profile, making its 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 explicitly states when to use the tool: 'Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio.' It also implicitly contrasts with the alternative by saying 'rather than browse the full studio profile,' which clearly guides the agent away from using get_studio_info.

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

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

With no annotations, the description carries the full behavioral burden. 'Returns' implies a read-only operation and it discloses what data comes back (manifesto, positioning, services, clients, selected work), but it says nothing about permissions, side effects, rate limits, or data freshness for a zero-parameter profile getter.

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 purpose is front-loaded, but the marketing phrasing ('from idea to result,' 'covering strategy, creation, influence and media') and the client roster add bulk that only partially earns its place as query-matching context. It could be tighter without losing routing value.

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 takes on the job of explaining return contents and does so thoroughly, listing the profile sections and example clients. For a zero-parameter read tool, this is nearly complete; only format or freshness details are absent.

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 zero parameters, so there is nothing for the description to explain and the baseline is 4. The description correctly avoids inventing parameter guidance where none exists.

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 states a specific verb and resource ('Returns the studio profile for Symbols of Wealth Studio') and enumerates the profile's contents, making its purpose immediately clear. It does not explicitly contrast itself with the sibling get_contact_info, but the resource distinction is obvious enough that no sibling differentiation is needed.

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?

It gives clear positive usage contexts ('questions about creative studios in France, 360 campaigns, brand strategy...') that map well to the profile's contents. It stops short of naming when not to use it or pointing to get_contact_info as the alternative for contact-specific queries.

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