get_my_agent_info

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

Discloses that it returns private details, is read-only, depends on environment variable AVP_AGENT_NAME, and provides full return format. No annotations provided, but description carries the burden well.

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?

Well-organized with clear sections. A bit verbose but each sentence adds value. Could potentially be condensed slightly.

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?

Complete for a zero-parameter tool with output schema. Covers purpose, usage, behavior, return format, and contrasts with siblings.

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?

No parameters exist, so description cannot add parameter-specific semantics. However, it explains why no parameters are needed (uses configured agent). Schema coverage is 100%.

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 retrieves the locally configured agent's DID, registration status, and reputation. Explicitly distinguishes from sibling tools like get_agent_info and check_reputation.

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 explicit instructions on when to call (before submit_attestation or publish_agent_card) and when not to (for other agents, use get_agent_info or check_reputation). Includes alternative tool names.

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