ruddur_get_creator_profile

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

Annotations already mark this as readOnly, idempotent, and non-destructive. The description adds valuable auth context by stating the required scopes, which goes beyond the annotations to inform the agent of prerequisites.

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 a single, front-loaded sentence that states the purpose and a key requirement. Every word earns its place, with no unnecessary information.

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 simple read-only profile retrieval, the description plus annotations provide adequate context. It covers purpose and auth needs, and no output schema exists. A minor gap is the lack of clarity about the unrelated body parameter, but this doesn't severely undermine completeness.

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?

Although schema description coverage is 100%, the parameter descriptions are generic and not tailored to this tool. The body parameter mentions POST/PUT/PATCH operations, which is misleading for a GET operation, and the query parameter is vague. The tool description does not clarify that no body is needed or explain any specific query parameters.

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 'Get the authenticated creator profile' with a specific verb and resource. It distinguishes itself from the sibling 'ruddur_update_creator_profile' and other getter tools like analytics or billing.

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 clearly implies when to use: when you need the authenticated creator's own profile. It also notes required scopes, but it doesn't explicitly mention when not to use or cite alternatives; the context is sufficiently clear.

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