ecash_get_agent

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 behavioral disclosure. It only states 'Get the profile,' which implies a read operation, but does not explicitly confirm read-only behavior, error handling, permissions, or return format. This is insufficient for a tool with no annotation safety signals.

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 one short, front-loaded sentence: 'Get the profile of a specific agent by their address.' No words are wasted, and it immediately conveys the action and target.

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 has no output schema or annotations, and the description provides only the basic action without explaining what a 'profile' contains, possible error cases, or how it differs from the similarly named sibling 'ecash_get_agent_info.' Given this ambiguity, the description is not complete enough for confident invocation in all situations.

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 fully describes the single parameter 'address' with the description 'The agent address to look up,' giving 100% coverage. The tool description repeats 'by their address' without adding any extra meaning beyond the schema, so a baseline score of 3 is appropriate.

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 tool's function: 'Get the profile of a specific agent by their address.' It uses a specific verb and resource, but does not differentiate from the similarly named sibling tool 'ecash_get_agent_info', so it lacks sibling differentiation.

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 guidance on when to use this tool versus alternatives, such as 'ecash_get_agent_info' or 'ecash_find_agents'. It simply explains what the tool does, leaving the agent to guess which lookup tool is appropriate.

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