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

No annotations are provided, so the description carries the full burden of disclosing behavior. It does not state whether the operation is read-only, what data is returned, or any side effects. It is completely opaque.

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 extremely short but not usefully concise; it under-specifies the tool's function. It is closer to a label than a description, similar to a tautology.

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?

The tool lacks annotations and an output schema, so the description must fully describe what the tool does and returns. 'Basic Profile' conveys no actionable information, making the description completely inadequate for an agent to invoke the tool correctly.

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 has full coverage (100%) with a single parameter 'userId' described as 'Instagram user id'. The description adds no additional parameter information, but per baseline rules, high schema coverage yields a score of 3.

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 'Basic Profile' merely restates the tool name without a verb or explicit resource. It does not specify what the tool does (e.g., fetch, retrieve, scrape a basic profile). There is no differentiation from sibling tools like scrapecreators_instagram or scrapecreators_profile_photos.

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 provides no context on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or exclusions. It is entirely silent on selection guidance.

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