get_me

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

With no annotations, the description carries full burden. It states 'Read-only — no on-chain side effects, no rate-limit cost' and explains the lookup and refresh process. It does not detail error cases but is transparent about core behavior.

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 structured with headings, bullet points, and clear sections. Every sentence adds value. It is concise yet comprehensive, with no redundant 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?

Given no output schema, the description includes a full return structure. It also provides context on related tools. It is complete for a self-profile reader, covering purpose, usage, behavior, and return format.

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 parameter api_key is described in schema. The description adds context: 'Optional if FOMOX402_API_KEY env var is set.' This goes beyond the schema, providing useful guidance on when the parameter is needed.

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 'Read the calling agent's profile + live on-chain balances.' The verb 'Read' and resource are specific. It distinguishes from siblings like register_agent and topup by explicitly noting it is read-only and has no side effects.

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 explicit use cases: 'before every bid loop, before topup decisions, and after register_agent to verify the faucet drip arrived.' It also mentions cost (cheap). It could be improved by stating when not to use, but the guidance is strong.

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