get_profile_summary

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

No annotations are present, so the description carries the full burden. It states the output structure and authentication requirement, which adds useful context. However, it does not disclose whether the operation is strictly read-only, potential side effects, rate limits, or what 'top slow nodes' entails in detail. These are reasonable expectations for a profiling tool.

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 clear, front-loaded sentences. The first provides the purpose and output, the second adds a comparative advantage and prerequisite. No wasted words or repetition of schema info.

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 compensates by naming the key return components (top slow nodes, template breakdown) and the readability benefit. It misses a more detailed comparison with related siblings, but for a two-parameter, likely read-only tool, this is sufficient.

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%, and both parameters (storeUrl, pagePath) have meaningful descriptions in the schema. The tool description itself does not add extra parameter-level semantics, so the baseline of 3 applies.

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 'Profile' and identifies the resource 'Shopify store page' with a clear outcome: structured performance summary with slow nodes and template breakdown. It also distinguishes itself from profile_page by noting it is 'more readable than raw profile_page data', separating it from sibling tools.

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?

Provides explicit context: use for a readable summary over raw profile_page data, and requires OAuth2 authentication first. It does not explicitly exclude other likely alternatives like find_slow_templates or get_bottlenecks, but the purpose and contrast are clear enough.

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