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

Annotations already indicate readOnlyHint=true, so the description's value is in clarifying the return content (profile and canonical URL) and the withTimeline option. It does not disclose any additional side effects or limitations (e.g., null profile if not found), but is consistent with annotations.

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 primary action, no filler. Every word adds value: action, resource, key parameter, return info. Highly efficient.

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 the presence of an output schema and annotations, the description covers the main functionality and optional behavior. It does not mention error handling or edge cases, but for a read-only tool with clear parameters, it is largely sufficient. Minor missing details like locale explanation could improve 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?

Schema description coverage is 0%, so the description must compensate. It explains that withTimeline includes recent events, and implies slug is the identifier. Locale and type are not detailed, but type enums ('person', 'organization') are self-explanatory. Some parameters lack elaboration, but core ones are covered.

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 it fetches a profile for a person or organization by slug, with an optional timeline. It identifies the specific resource (Pollar profile) and action (fetch). However, it does not explicitly distinguish this tool from siblings like get_event or get_live_story, but the entity focus is clear.

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?

Usage is implied by the description: use when you need a Pollar entity profile. No explicit guidance on when to avoid it or switch to alternatives. Sibling tools cover events, stories, etc., but the description does not contrast them.

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