get_user_referrer

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

No annotations provided; description discloses auth restrictions (project API key only), null field behavior, and that it reflects PUT assignments. Lacks mention of rate limits or pagination, but sufficient for a read-only operation.

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?

Packed with useful info (path, return fields, comparison, auth, example) but could be slightly trimmed. Front-loaded with purpose.

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?

Covers return fields, auth, example, and comparison despite no output schema and low schema coverage. Completeness is adequate for a simple read tool.

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 coverage is only 33% (only project_api_key described), but description adds meaning through example and explanation of fallback for project_api_key and enumeration of user_identifier_type, compensating for missing schema descriptions.

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?

Clearly states it reads a user referrer, includes HTTP method and path, and differentiates from sibling tool by explaining the difference in behavior with referral_code_uses.

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?

Provides context by comparing to another endpoint and specifying auth requirements, but does not explicitly list when not to use it or other alternatives.

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