profile_page

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

With no annotations provided, the description carries the burden. It discloses the authentication requirement and the output type (full flame graph). However, it does not explicitly state whether the operation is read-only, any potential performance impact on the store, or the format of the flame graph data. The reference to the Chrome extension provides some context but leaves room for more transparency.

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, front-loaded with the action and purpose. The first sentence immediately states what the tool does; the second provides output type and auth requirement. Every clause earns its place with no redundancy or filler.

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 no output schema, the description adequately conveys the return type ('FULL flame graph profiling data') and references the Chrome extension for familiarity. It covers the key context: purpose, prerequisites, and output. It does not detail edge cases or error handling, but for a straightforward profiling tool with two simple parameters, this is reasonably 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?

The input schema already covers 100% of parameter descriptions (storeUrl and pagePath), so the baseline is 3. The tool description adds little beyond the schema, only implying the target is a store page. No extra semantic nuance is added, but the schema is sufficiently clear on its own.

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's purpose: 'Profile a Shopify store page to analyze Liquid template rendering performance.' It uses a specific verb ('Profile') and resource ('Shopify store page'), and distinguishes from siblings like get_profile_summary (which likely provides a summary) and find_slow_templates (which targets slow templates).

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 the prerequisite: 'Requires OAuth2 authentication first (use the 'login' tool).' This tells the agent when to use this tool (after login) and provides an alternative for the auth step. It also hints at when to use this over summary tools by saying it returns 'FULL flame graph profiling data,' implying it's for detailed analysis rather than high-level summaries.

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