get_edge_function_logs

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

No annotations provided, so description must disclose behavior. It only says 'Get logs', without explaining whether it returns live or historical logs, pagination, rate limits, or any side effects. The read-only nature is not explicitly stated.

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?

Single sentence, very concise. No unnecessary words. However, it could be slightly expanded (e.g., one more sentence on usage) without losing conciseness.

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?

For a simple two-parameter tool with no output schema, the description is too minimal. It does not specify return format (e.g., array of log objects), whether logs are real-time or historical, or any filtering beyond 'limit'. An agent needs more context to use it effectively.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds no additional context beyond the schema. Baseline 3 is appropriate as schema handles documentation, but no extra value from description.

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?

Description clearly states 'Get logs for an edge function', specifying the action (get logs) and resource (edge function). This distinguishes it from sibling tools like 'list_edge_functions' (list functions) and 'invoke_edge_function' (invoke function).

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?

No guidance on when to use this tool over alternatives. No mention of prerequisites, limitations, or scenarios where another tool might be better. For example, it does not advise checking if the function exists first or differentiate from 'invoke_edge_function'.

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