get_author_by_slug

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

There are no annotations, so the description must carry the full behavioral burden, but it discloses only the basic fetching action. It does not mention error behavior, not-found cases, response shape, or whether the profile is a summary or full profile.

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?

One tightly scoped sentence with the essential information and a useful example. No filler or redundancy; the purpose and input format are 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 single-parameter lookup tool, the basic context is present. However, without an output schema or annotations, details about expected return value and failure modes are absent, making it adequate but not 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 schema already documents 'slug' at 100% coverage, but the description enhances it by providing a realistic example ('brandon-sanderson') that clarifies the expected URL slug format. This adds value beyond the schema.

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 verb 'Get', the resource 'author's profile', and the lookup mechanism 'URL slug', with a concrete example. This distinguishes it from siblings like get_author_by_id and get_author_books by specifying the slug-based identity.

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?

No guidance is provided about when to use this tool versus alternatives such as get_author_by_id or get_author_books. The description gives no contexts, exclusions, or preference signals.

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