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

With no annotations, the description carries the full burden. It usefully discloses the returned content (all statuses plus review notes) and notes that submission is auth-gated and moderated, but says nothing about whether this listing itself requires auth, whether results are paginated, or their ordering.

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?

Two tight sentences with the core scope front-loaded. The second sentence about the POST submission route is slightly off-scope for a listing tool, but it earns its place by preventing a mistaken submit attempt through this tool.

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?

No output schema and no annotations mean the description must cover return shape; it names the statuses and review notes but omits pagination, ordering, and whether an empty list or auth failure is possible. Adequate for a zero-parameter lister, but not complete.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call returning the caller's own submissions.

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?

States a specific verb and resource with scope: 'Agent profiles you submitted (any status: pending, approved, rejected)'. The 'you submitted' qualifier cleanly separates it from search_agents/get_agent, though it never names those siblings explicitly.

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?

Implies the use case (reviewing your own submissions and their review notes) and redirects submission to POST /api/v1/agents. It gives no explicit when-not guidance and does not name get_agent or search_agents as alternatives for viewing other agents.

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