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

Annotations already establish readOnly, non-destructive, closed-world, so the safety profile is covered; the description adds OAuth requirement, the fact that story content is read-only via remote MCP, and the imagesHasMore pagination signal. Those are real behavioral facts not present in annotations or schema.

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?

Front-loaded with the when-to-use condition, then editing route, then pagination fallback. Most sentences carry weight, but 'The image IDs support reorder and dashboard removal review' is vague about what the agent should actually do and could be tightened or dropped.

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?

An output schema exists, so return shape need not be explained; the description covers auth, edit-routing, and pagination follow-up. The only loose end is not distinguishing this tool from get_public_profile or list_public_profiles when the caller's intent is ambiguous.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It does explain how to react to the imagesHasMore output field, which is a useful cue even though the output schema defines it.

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?

States a specific verb-resource pair ('get_profile' for the signed-in user's own Daylily Catalog profile) and enumerates the content surfaced: storefront copy, slug, location, images, public profile content. The phrase 'their own' implicitly separates it from get_public_profile, though the sibling is never named outright.

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?

Gives a concrete trigger ('signed-in user asks about their own profile'), routes edits to open_dashboard with edit_profile_content, and routes image discovery to daylily.list_images when imagesHasMore is true. It does not say when to use get_public_profile instead, which is the other obvious alternative.

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